From: Robert Love <rml@tech9.net>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: Dipankar Sarma <dipankar@in.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Read-Copy Update 2.5.4-pre2
Date: 08 Feb 2002 18:54:02 -0500 [thread overview]
Message-ID: <1013212443.806.196.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.33.0202081847020.30304-100000@coffee.psychology.mcmaster.ca>
In-Reply-To: <Pine.LNX.4.33.0202081847020.30304-100000@coffee.psychology.mcmaster.ca>
On Fri, 2002-02-08 at 18:51, Mark Hahn wrote:
> yes, but have you evaluated whether it's noticably better than
> other forms of locking? for instance, couldn't your dcache example
> simply use BR locks?
Good point.
One of the things with implicit locking schemes like RCU is that the
performance hit merely shifts. Reading the data may no longer have any
overhead, but the hit is taken elsewhere. One most be careful in
benchmarking RCU locking.
Robert Love
next prev parent reply other threads:[~2002-02-08 23:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 18:12 [PATCH] Read-Copy Update 2.5.4-pre2 Dipankar Sarma
2002-02-08 23:51 ` Mark Hahn
2002-02-08 23:54 ` Robert Love [this message]
2002-02-09 6:56 ` Dipankar Sarma
2002-02-09 8:30 ` Andrea Arcangeli
2002-02-09 6:18 ` Dipankar Sarma
2002-02-09 23:19 ` Pavel Machek
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=1013212443.806.196.camel@phantasy \
--to=rml@tech9.net \
--cc=dipankar@in.ibm.com \
--cc=hahn@physics.mcmaster.ca \
--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