public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Arjan van de Ven <arjanv@redhat.com>,
	"Martin J. Bligh" <mbligh@aracnet.com>,
	"Nakajima, Jun" <jun.nakajima@intel.com>,
	Andrew Morton <akpm@osdl.org>, Anton Blanchard <anton@samba.org>,
	linux-kernel@vger.kernel.org
Subject: Re: CONFIG_IRQBALANCE for AMD64?
Date: Fri, 28 May 2004 13:14:40 -0700	[thread overview]
Message-ID: <40B79DB0.6090209@us.ibm.com> (raw)
In-Reply-To: <40B799EB.8060000@pobox.com>

Jeff Garzik wrote:
> Nivedita Singhvi wrote:

> Network is one of the areas where you _don't_ want to be constantly 
> pointing your NIC's irq to different CPUs.
> 
> Cache affinity, packet re-ordering problems, and other fun ensue.
> 
>     Jeff

I agree that there is a tradeoff point - we need the cache
affinity, but you also want to employ the other CPUs which
might be idle in the system - so there is a timeframe that
is ideal to have one CPU pick up interrupts, and then move
on to another - but that timeframe is surely shorter than
then every 5 mins or so that the irq daemon might run,
correct?

Also, yep, packet re-ordering is an issue for TCP connections,
and we do have mechanisms in the kernel to address it to some
extent - so we don't trigger fast retransmit unnecessarily.
And if you have a lot of UDP and other traffic, or short lived
connections, then you are unnecessarily subjecting them to
a less ideal environment.

I agree that this is very tricky stuff to optimize, and I
certainly don't know how to go about picking the best
heuristic here, but I am wondering how the frequency with
which a user space daemon might run (and you don't want it
to run too often given the cost) would be able to handle
something that does require finer granularity. Or is it
everybody's understanding that fine grained balancing is
not needed?

thanks,
Nivedita




  reply	other threads:[~2004-05-28 20:13 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 17:09 CONFIG_IRQBALANCE for AMD64? Nakajima, Jun
2004-05-28 17:40 ` Jeff Garzik
2004-05-28 17:45   ` Arjan van de Ven
2004-05-28 17:46   ` Martin J. Bligh
2004-05-28 17:57     ` Arjan van de Ven
2004-05-28 19:51       ` Nivedita Singhvi
2004-05-28 19:58         ` Jeff Garzik
2004-05-28 20:14           ` Nivedita Singhvi [this message]
2004-05-28 21:45             ` Jeff Garzik
2004-05-28 20:03         ` Arjan van de Ven
  -- strict thread matches above, loose matches on Subject: below --
2004-05-28 23:37 Nakajima, Jun
2004-05-28 22:05 Nakajima, Jun
2004-05-28 22:54 ` Andi Kleen
2004-05-29  1:27   ` Nick Piggin
2004-05-29 10:06     ` Andi Kleen
2004-05-29 10:10       ` Nick Piggin
2004-05-29 11:18         ` Andi Kleen
     [not found] <20Uhn-7bP-11@gated-at.bofh.it>
     [not found] ` <20UqZ-7i7-5@gated-at.bofh.it>
2004-05-28 21:45   ` Andi Kleen
2004-05-28 18:20 Nakajima, Jun
2004-05-28 18:33 ` Martin J. Bligh
2004-05-28 18:44   ` Arjan van de Ven
2004-05-28 18:57     ` Martin J. Bligh
2004-05-28 19:01       ` Arjan van de Ven
2004-05-29  8:38     ` michael
2004-05-29  8:41     ` michael
2004-05-29  8:45       ` Arjan van de Ven
2004-05-27  3:48 Thomas Zehetbauer
2004-05-27  5:13 ` Jeff Garzik
2004-05-27 16:36   ` Thomas Zehetbauer
2004-05-27 16:50     ` Arjan van de Ven
2004-05-27 21:37       ` Chris Wedgwood
2004-05-27 17:03     ` Anton Blanchard
2004-05-27 22:36       ` Thomas Zehetbauer
2004-05-28  5:57         ` Arjan van de Ven

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=40B79DB0.6090209@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=arjanv@redhat.com \
    --cc=jgarzik@pobox.com \
    --cc=jun.nakajima@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.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