This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/13701] pthread_rwlock_rdlock & realtime scheduling writer lock precedence
- From: "bruno at clisp dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 04 Jan 2017 19:53:48 +0000
- Subject: [Bug nptl/13701] pthread_rwlock_rdlock & realtime scheduling writer lock precedence
- Auto-submitted: auto-generated
- References: <bug-13701-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13701
--- Comment #8 from Bruno Haible <bruno at clisp dot org> ---
(In reply to Torvald Riegel from comment #7)
> we're certainly not going to track which reader exactly has acquired a
> particular rdlock
It could be done by allocating a variable in thread-local storage
(pthread_key_create). But I agree that such an implementation would be costly
in pthread_rwlock_init (since pthread_key_create does a linear search).
--
You are receiving this mail because:
You are on the CC list for the bug.