From: Jonathan Lahr <lahr@sequent.com>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Jonathan Lahr <lahr@sequent.com>, linux-kernel@vger.kernel.org
Subject: Re: kernel lock contention and scalability
Date: Mon, 5 Mar 2001 10:41:18 -0800 [thread overview]
Message-ID: <20010305104118.C6212@w-lahr.des.sequent.com> (raw)
In-Reply-To: <20010215104656.A6856@w-lahr.des.sequent.com> <3A98D5D3.6A6B6686@colorfullife.com>
In-Reply-To: <3A98D5D3.6A6B6686@colorfullife.com>; from manfred@colorfullife.com on Sun, Feb 25, 2001 at 10:52:19AM +0100
Manfred Spraul [manfred@colorfullife.com] wrote:
>
> > lock contention work would be appreciated. I'm aware of timer scalability
> > work ongoing at people.redhat.com/mingo/scalable-timers, but is anyone
> > working on reducing sem_ids contention?
>
> Is that really a problem?
> The contention is high, but the actual lost time is quite small.
I agree it isn't a major performance problem under that workload. But, I
thought since the contention was high that other workloads which may
utilize it more might have shown it to be a significant problem.
> I've attached 2 changes that might reduce the contention, but it's just
> an idea, completely untested.
Thanks for the insight into the sempahore subsystem and the suggested fixes.
--
Jonathan Lahr
IBM Linux Technology Center
Beaverton, Oregon
lahr@us.ibm.com
503-578-3385
next prev parent reply other threads:[~2001-03-05 18:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 18:46 Jonathan Lahr
2001-02-25 9:52 ` Manfred Spraul
2001-03-05 18:41 ` Jonathan Lahr [this message]
2001-03-05 0:38 ` Anton Blanchard
2001-03-06 22:45 ` Jonathan Lahr
2001-03-06 23:39 ` Matthew Kirkwood
2001-03-07 0:28 ` Tim Wright
2001-03-07 3:12 ` Jeff Dike
2001-03-07 22:13 ` Tim Wright
2001-03-08 23:26 ` Jeff Dike
2001-03-11 6:50 ` Anton Blanchard
2001-03-11 6:26 ` Anton Blanchard
[not found] <98454d$19p9h$1@fido.engr.sgi.com>
2001-03-07 2:55 ` Rajagopal Ananthanarayanan
2001-03-07 5:48 ` Jeff Dike
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=20010305104118.C6212@w-lahr.des.sequent.com \
--to=lahr@sequent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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®