From: Keith Owens <kaos@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.6.6-rc2 Allow architectures to reenable interrupts on contended spinlocks
Date: Tue, 27 Apr 2004 15:19:37 +1000 [thread overview]
Message-ID: <4045.1083043177@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 26 Apr 2004 21:49:52 MST." <20040426214952.333c9ad7.akpm@osdl.org>
On Mon, 26 Apr 2004 21:49:52 -0700,
Andrew Morton <akpm@osdl.org> wrote:
>Keith Owens <kaos@sgi.com> wrote:
>>
>> Enable interrupts while waiting for a disabled spinlock, but only if
>> interrupts were enabled before issuing spin_lock_irqsave(). It makes a
>> measurable difference to interrupt servicing on large systems.
>
>Do you know which are the offending locks?
Workload dependent. We already service interrupts while waiting for a
non-disabled spinlock. The patch allows a cpu to do some useful work
and service interrupts while waiting for disabled spinlocks as well.
>How much difference, and how large are the systems?
>From memory (September 2003) 3-5% improvement on an AIM7 run, with 64
processors.
next prev parent reply other threads:[~2004-04-27 5:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 1:59 [patch] 2.6.6-rc2 Allow architectures to reenable interrupts on contended spinlocks Keith Owens
2004-04-27 4:49 ` Andrew Morton
2004-04-27 5:19 ` Keith Owens [this message]
2004-04-27 6:54 ` Benjamin Herrenschmidt
2004-04-27 7:45 ` Keith Owens
2004-04-27 11:36 ` Paul Mackerras
2004-04-27 12:05 ` Keith Owens
2004-04-27 12:33 ` Christoph Hellwig
2004-04-27 16:01 ` Linus Torvalds
2004-04-28 3:29 ` [patch] 2.6.6-rc3 " Keith Owens
2004-04-30 7:07 ` Andrew Morton
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=4045.1083043177@kao2.melbourne.sgi.com \
--to=kaos@sgi.com \
--cc=akpm@osdl.org \
--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