public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Arjan van de Ven <arjan@infradead.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
	Erik Mouw <erik@harddisk-recovery.com>,
	Lee Revell <rlrevell@joe-job.com>,
	"Martin J. Bligh" <mbligh@mbligh.org>,
	"Robert M. Stockmann" <stock@stokkie.net>,
	linux-kernel@vger.kernel.org, Randy Dunlap <rddunlap@osdl.org>,
	Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	Andre Hedrick <andre@linux-ide.org>,
	Manfred Spraul <manfreds@colorfullife.com>,
	Alan Cox <alan@redhat.com>, Kamal Deen <kamal@kdeen.net>
Subject: Re: irqbalance mandatory on SMP kernels?
Date: Thu, 20 Apr 2006 17:43:31 +1000	[thread overview]
Message-ID: <44473BA3.6090709@yahoo.com.au> (raw)
In-Reply-To: <1145457937.3085.49.camel@laptopd505.fenrus.org>

Arjan van de Ven wrote:
> On Wed, 2006-04-19 at 10:38 -0400, Theodore Ts'o wrote:
> 
>>On Wed, Apr 19, 2006 at 04:23:14PM +0200, Arjan van de Ven wrote:
>>
>>>as long as the irqs are spread the apaches will (on average) follow your
>>>irq to the right cpu. Only if you put both irqs on the same cpu you have
>>>an issue
>>
>>Maybe I'm being stupid but I don't see how the Apache's will follow
>>the IRQ's to the right CPU.  I agree this would be a good thing to do,
>>but how does the scheduler accomplish this?
> 
> 
> iirc this part of the kernel uses wake_up_sync() and such, which tend to
> pull the apache to the cpu (if it's idle) in the long term
> (or it ought to; at one point it did)

Yeah it has "affine wakeups" now, which will do that for all
types of wakeups, and not just to idle CPUs either (sync
wakeups just get pulled a little more strongly).

IIRC SGI reported something like a factor 8 improvement in
CPU efficiency on a database IO simulation on a smallish
system (16-way maybe).

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2006-04-20 16:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-17 13:00 irqbalance mandatory on SMP kernels? Robert M. Stockmann
2006-04-17 13:10 ` Arjan van de Ven
2006-04-17 14:15   ` Robert M. Stockmann
2006-04-17 14:23     ` Arjan van de Ven
2006-04-17 14:31 ` Martin J. Bligh
2006-04-17 15:01   ` Lee Revell
2006-04-18 16:35     ` Theodore Ts'o
2006-04-18 17:42       ` Stephen Hemminger
2006-04-18 17:53       ` Martin Bligh
2006-04-18 18:19       ` Arjan van de Ven
2006-04-19 12:42         ` Erik Mouw
2006-04-19 14:23           ` Arjan van de Ven
2006-04-19 14:38             ` Theodore Ts'o
2006-04-19 14:45               ` Arjan van de Ven
2006-04-20  7:43                 ` Nick Piggin [this message]
2006-04-19 14:30           ` Martin J. Bligh

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=44473BA3.6090709@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=alan@redhat.com \
    --cc=andre@linux-ide.org \
    --cc=arjan@infradead.org \
    --cc=erik@harddisk-recovery.com \
    --cc=kamal@kdeen.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfreds@colorfullife.com \
    --cc=mbligh@mbligh.org \
    --cc=rddunlap@osdl.org \
    --cc=rlrevell@joe-job.com \
    --cc=stock@stokkie.net \
    --cc=torvalds@osdl.org \
    --cc=tytso@mit.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