From: Arjan van de Ven <arjan@infradead.org>
To: Joshua Hudson <joshudson@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: readers-writers mutex
Date: Thu, 06 Apr 2006 03:06:55 +0200 [thread overview]
Message-ID: <1144285616.3023.3.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <bda6d13a0604051521o229de77dvb38992d6427a450c@mail.gmail.com>
On Wed, 2006-04-05 at 15:21 -0700, Joshua Hudson wrote:
> Since we are moving from semaphores to mutex, there should be a
> mutex_rw.
should there really? We discussed this briefly during the mutex work
the conclusion was that rw_sems
1) are rare (thankfully; they're highly expensive)
2) do not have mutex semantics
so... can you explain how your rw_mutex is behaving different from an
rw_sem, and can you explain what the gains are for that conversion?
(eg for mutex it was better defined semantics, lots better debugging
(possible due to the semantics) and more performance). What is that for
rw_mutex ?
next prev parent reply other threads:[~2006-04-06 1:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 22:21 Joshua Hudson
2006-04-06 1:06 ` Arjan van de Ven [this message]
2006-04-06 1:59 ` Joshua Hudson
2006-04-06 1:15 ` Jeff V. Merkey
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=1144285616.3023.3.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=joshudson@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®