From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andi Kleen <ak@muc.de>
Cc: "David S. Miller" <davem@redhat.com>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org,
paul.mckenney@us.ibm.com, andrea@suse.de
Subject: Re: 8-CPU (SMP) #s for lockfree rtcache
Date: 28 May 2002 19:10:47 +0100 [thread overview]
Message-ID: <1022609447.4123.126.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20020528183409.A23001@averell>
On Tue, 2002-05-28 at 17:34, Andi Kleen wrote:
> And gain tons of new atomic_incs and decs everywhere in the process?
> I would prefer RCU.
RCU is a great way to make sure people get module unloading *wrong*. It
has to be simple for the driver authors. The odd locked operation on
things like open() of a device file is not a performance issue, not
remotely.
Lots of people write drivers, many of them not SMP kernel locking gurus
who have time to understand RCU and when they can or cannot sleep, and
what happens if their unload is pre-empted and RCU is in use. The kernel
core has to provide a clean easy interface. The network code is a superb
example of this. All the hard thinking is done outside of the driver, at
least unless you choose to join in that thinking to get the last scraps
of performance.
Alan
next prev parent reply other threads:[~2002-05-28 17:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 11:41 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 [this message]
2002-05-28 17:24 ` Andi Kleen
2002-05-29 4:44 ` Rusty Russell
2002-05-28 15:49 ` Robert Love
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
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=1022609447.4123.126.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ak@muc.de \
--cc=andrea@suse.de \
--cc=davem@redhat.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 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®