From: Robert Love <rml@tech9.net>
To: dipankar@in.ibm.com
Cc: "David S. Miller" <davem@redhat.com>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org,
Paul McKenney <paul.mckenney@us.ibm.com>,
Andrea Arcangeli <andrea@suse.de>
Subject: Re: 8-CPU (SMP) #s for lockfree rtcache
Date: 28 May 2002 08:49:58 -0700 [thread overview]
Message-ID: <1022600998.20317.44.camel@sinai> (raw)
In-Reply-To: <20020528182806.A21303@in.ibm.com>
On Tue, 2002-05-28 at 05:58, Dipankar Sarma wrote:
> > Thanks, I am convinced RCU is the way to go.
I am not. :P
> Well, the last time RCU was discussed, Linus said that he would
> like to see someplace where RCU clearly helps.
I agree the numbers posted are nice, but I remain skeptical like Linus.
Sure, the locking overhead is nearly gone in the profiled function where
RCU is used. But the overhead has just been _moved_ to wherever the RCU
work is now done. Any benchmark needs to include the damage done there,
too.
I also balk at implicit locking...
Robert Love
next prev parent reply other threads:[~2002-05-28 15:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 11:41 8-CPU (SMP) #s for lockfree rtcache Dipankar Sarma
2002-05-28 11:25 ` David S. Miller
2002-05-28 12:58 ` Dipankar Sarma
2002-05-28 12:40 ` David S. Miller
2002-05-28 15:45 ` Andi Kleen
2002-05-28 17:03 ` Alan Cox
2002-05-28 16:34 ` Andi Kleen
2002-05-28 18:10 ` Alan Cox
2002-05-28 17:24 ` Andi Kleen
2002-05-29 4:44 ` Rusty Russell
2002-05-28 15:49 ` Robert Love [this message]
2002-05-28 16:25 ` Dipankar Sarma
2002-05-28 17:09 ` Dipankar Sarma
2002-05-29 17:44 ` kuznet
2002-06-03 12:08 ` Dipankar Sarma
-- strict thread matches above, loose matches on Subject: below --
2002-05-28 19:57 Dipankar Sarma
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=1022600998.20317.44.camel@sinai \
--to=rml@tech9.net \
--cc=andrea@suse.de \
--cc=davem@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.mckenney@us.ibm.com \
--cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.