rwlock for async application

[Yann Droneaud]

Hi,

Le 25/03/2022 à 18:16, David Mozes a écrit :
> Hi all,
> I want to discuss some needs that I think need to address.
> On async coding used mainly on networking and storage applications, how ever I believe on other applications as well, what we are doing is acquiring a lock on the application level, and then call to the OS/kernel for sending/writing
> Callback instead of waitengin on blocking for the sending/writing to finish. After completing the OS, call the CB to release the transaction and the lock.
> The problem is that the current glibc implumnation doesn't support taking and releasing the writer lock from different threads.
>
> I think it needs to be address .
>   Actually I did the folwing change:


https://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_rwlock_unlock.html


"Results are undefined if the read-write lock /rwlock/ is not held by 
the calling thread"


Regards.

-- 

Yann Droneaud

OPTEYA