From: "David S. Miller" <davem@redhat.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: smp overhead, and rwlocks considered harmful
Date: 22 Mar 2003 19:39:31 -0800 [thread overview]
Message-ID: <1048390771.20776.5.camel@rth.ninka.net> (raw)
In-Reply-To: <20030322175816.225a1f23.akpm@digeo.com>
On Sat, 2003-03-22 at 17:58, Andrew Morton wrote:
> I've always been a bit skeptical about rwlocks - if you're holding the lock
> for long enough for a significant amount of reader concurrency, you're
> holding it for too long. eg: tasklist_lock.
I totally agree with you Andrew, on modern SMP systems rwlocks
are basically worthless. I think we should kill them off and
convert all instances to spinlocks or some better primitive (perhaps
a more generalized big reader lock, Roman Zippel had something...)
--
David S. Miller <davem@redhat.com>
next prev parent reply other threads:[~2003-03-23 3:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-23 1:58 Andrew Morton
2003-03-23 3:39 ` David S. Miller [this message]
2003-03-23 3:55 ` Anton Blanchard
2003-03-23 4:04 ` Andrew Morton
2003-03-23 6:25 ` Anton Blanchard
2003-03-23 12:33 ` Michael Vergoz
2003-03-23 15:17 ` Alan Cox
2003-03-23 21:43 ` Aaron Lehmann
2003-03-23 21:51 ` Andrew Morton
2003-03-23 6:34 Adam J. Richter
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=1048390771.20776.5.camel@rth.ninka.net \
--to=davem@redhat.com \
--cc=akpm@digeo.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®