From: "Theodore Ts'o" <tytso@mit.edu>
To: Arjan van de Ven <arjan@infradead.org>
Cc: 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: Wed, 19 Apr 2006 10:38:15 -0400 [thread overview]
Message-ID: <20060419143815.GH706@thunk.org> (raw)
In-Reply-To: <1145456594.3085.42.camel@laptopd505.fenrus.org>
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?
- Ted
next prev parent reply other threads:[~2006-04-19 14:38 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 [this message]
2006-04-19 14:45 ` Arjan van de Ven
2006-04-20 7:43 ` Nick Piggin
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=20060419143815.GH706@thunk.org \
--to=tytso@mit.edu \
--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 \
/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