mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
	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 16:23:14 +0200	[thread overview]
Message-ID: <1145456594.3085.42.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060419124210.GB24807@harddisk-recovery.com>

On Wed, 2006-04-19 at 14:42 +0200, Erik Mouw wrote:
> On Tue, Apr 18, 2006 at 08:19:17PM +0200, Arjan van de Ven wrote:
> > > but spreading IRQ's across all of the CPU's doesn't seem like it's
> > > ever the right answer.
> > 
> > well it is in some cases, imagine having 2 cpus and 2 gige nics that are
> > very busy doing webserving. That's an obvious case where 1-nic-per-cpu
> > ends up doing the right thing... the way it ends up is that each nic has
> > a full cpu for itself and it's own apaches... almost fully independent
> > of the other one. Now if you moved both irqs to the same cpu, the
> > apaches would follow, because if they didn't then you'd be bouncing
> > their data *all the time*. And at that point the other cpu will become
> > bored ;)
> 
> So what happens with a dual amd64 system where each CPU has its "own"
> NIC? Something like this:

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



  reply	other threads:[~2006-04-19 14:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-17 13:00 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 [this message]
2006-04-19 14:38             ` Theodore Ts'o
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=1145456594.3085.42.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=akpm@osdl.org \
    --cc=alan@redhat.com \
    --cc=andre@linux-ide.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

all inboxes | Powered by JetHome®