From: William Lee Irwin III <wli@holomorphy.com>
To: Robert Love <rml@tech9.net>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Alexander Viro <viro@math.psu.edu>,
mbligh@aracnet.com, ahu@ds9a.nl, peter@chubb.wattle.id.au,
jw@pegasys.ws, linux-kernel@vger.kernel.org
Subject: Re: ps performance sucks (was Re: dcache_rcu [performance results])
Date: Thu, 7 Nov 2002 20:29:25 -0800 [thread overview]
Message-ID: <20021108042925.GD23425@holomorphy.com> (raw)
In-Reply-To: <1036729047.765.2887.camel@phantasy>
On Thu, 2002-11-07 at 22:57, William Lee Irwin III wrote:
>> I'm not sure RCU would help this any; I'd be very much afraid of the
>> writes being postponed indefinitely or just too long in the presence
>> of what's essentially perpetually in-progress read access. Does RCU
>> have a guarantee of forward progress for writers?
On Thu, Nov 07, 2002 at 11:17:21PM -0500, Robert Love wrote:
> I am not sure I like the idea of RCU for the tasklist_lock.
> I do agree 100% with your first point, though - the problem is
> ill-behaved readers. I think the writing vs. reading is such that the
> rw-lock we have now is fine, we just need to make e.g. /proc play way
> way more fair.
This is only feasible for small numbers of cpus. Any compensation
provided by algorithmic improvements on the read-side is outweighed by
NR_CPUS. Making readers well-behaved only solves half of the issue.
Whether the other half is addressible in a 2.6.x time scale is an open
question, but a question I'd like to see answered in favor of fixing
the livelocks sooner rather than later (esp. as 2.7+ issues are unlikely
to be resolved in line with hardware release schedules). I have a
strong bias toward code which works everywhere, all the time.
Bill
next prev parent reply other threads:[~2002-11-08 4:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <993103655@toto.iv>
2002-11-05 22:49 ` ps performance sucks (was Re: dcache_rcu [performance results]) Peter Chubb
2002-11-06 0:06 ` Martin J. Bligh
2002-11-05 23:16 ` bert hubert
2002-11-06 0:57 ` Martin J. Bligh
2002-11-06 0:10 ` bert hubert
2002-11-06 1:23 ` Martin J. Bligh
2002-11-06 0:34 ` Alexander Viro
2002-11-07 12:06 ` Rusty Russell
2002-11-08 3:57 ` William Lee Irwin III
2002-11-08 4:17 ` Robert Love
2002-11-08 4:27 ` Daniel Jacobowitz
2002-11-08 4:29 ` William Lee Irwin III [this message]
2002-10-30 10:49 [PATCH 2.5.44] dcache_rcu Maneesh Soni
2002-10-31 10:53 ` dcache_rcu [performance results] Dipankar Sarma
2002-11-02 1:36 ` Andrew Morton
2002-11-02 9:13 ` Dipankar Sarma
2002-11-04 17:29 ` Martin J. Bligh
2002-11-05 0:00 ` jw schultz
2002-11-05 1:14 ` ps performance sucks (was Re: dcache_rcu [performance results]) Martin J. Bligh
2002-11-05 3:57 ` Werner Almesberger
2002-11-05 4:42 ` Erik Andersen
2002-11-05 5:44 ` Martin J. Bligh
2002-11-05 5:59 ` Alexander Viro
2002-11-05 6:05 ` Martin J. Bligh
2002-11-05 6:15 ` Robert Love
2002-11-05 6:13 ` Erik Andersen
2002-11-05 6:14 ` Werner Almesberger
2002-11-05 4:26 ` jw schultz
2002-11-05 5:51 ` Martin J. Bligh
2002-11-05 19:57 ` Kai Henningsen
2002-11-05 21:33 ` Erik Andersen
2002-11-05 22:09 ` Karim Yaghmour
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=20021108042925.GD23425@holomorphy.com \
--to=wli@holomorphy.com \
--cc=ahu@ds9a.nl \
--cc=jw@pegasys.ws \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=peter@chubb.wattle.id.au \
--cc=rml@tech9.net \
--cc=rusty@rustcorp.com.au \
--cc=viro@math.psu.edu \
/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