public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjmunroe at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/7057] pthread rwlock does not implement 'writer preferred' option
Date: Sun, 30 Nov 2008 17:35:00 -0000	[thread overview]
Message-ID: <20081130173348.9485.qmail@sourceware.org> (raw)
In-Reply-To: <20081126155626.7057.udig@il.ibm.com>


------- Additional Comments From sjmunroe at us dot ibm dot com  2008-11-30 17:33 -------
Uli I think this question deserves a more complete explanation. 

This seems like a reasonable request. If you disagree then it would not hurt 
to explain why.

There seems to be a valid concern related to reliable implementation of 
recursive read locks with writer priority. As in this discusion:

http://sources.redhat.com/ml/libc-alpha/2000-01/msg00055.html

If this your concern then saying so would help resolve/close this issue.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bmark at us dot ibm dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=7057

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2008-11-30 17:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-26 15:57 [Bug nptl/7057] New: " udig at il dot ibm dot com
2008-11-26 16:11 ` [Bug nptl/7057] " drepper at redhat dot com
2008-11-30 17:35 ` sjmunroe at us dot ibm dot com [this message]
     [not found] <bug-7057-131@http.sourceware.org/bugzilla/>
2014-07-01 21:11 ` fweimer at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081130173348.9485.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).