public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Andi Kleen <ak@muc.de>, "Martin J. Bligh" <mbligh@aracnet.com>,
	linux-kernel@vger.kernel.org
Subject: Re: CONFIG_IRQBALANCE for AMD64?
Date: 29 May 2004 00:54:26 +0200
Date: Sat, 29 May 2004 00:54:26 +0200	[thread overview]
Message-ID: <20040528225426.GA89095@colin2.muc.de> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D372001730182BC35@scsmsx402.amr.corp.intel.com>

On Fri, May 28, 2004 at 03:05:48PM -0700, Nakajima, Jun wrote:
> >At least the AMD chipsets found in most Opteron boxes need software
> >balancing too.
> 
> Actually lowest priority delivery works on P4 and AMD (I did not tested
> it on AMD, though), if we _update_ TPR. But I don't recommend that,

True. I remember there was even a patch for that from James C. long ago.
I considered at one point to add it to x86-64, but ended up 
not doing anything and just recommending irqbalanced.

[I didn't test it neither, so no guarantee TPR really works on AMD]

> instead we should implement the similar or optimized behavior in
> software because "soft TPR" can be more efficient and scalable. And I
> think this is something in my mind, and I think the kernel should do it.

I'm not convinced of that. At least the current i386 implemention
is basically a kernel thread that wakes up regularly, reads some
statistics and then updates the APIC.

There is not much reason this cannot be done in user space, and
user space has the advantage that more advanced heuristics (which
I'm sure will be there) can be more easily implemented.

And handling all interrupts at CPU #0 during early boot up is 
not really an issue.

An kernel implementation may make sense when you're doing something
really dynamic: e.g. not just a timer, but dynamically redirecting
network interrupts to the CPU the process who will read from the
socket runs on. Obviously it would need kernel support for that, since
user space could not keep up with such a high sampling rate. But that's
future research work (if it can be even done generically at all)
and I don't see it on the radar screen anytime soon. We first need to solve
the NUMA scheduling problem, which is already hard enough ;-) 

And for the simpler heuristics that don't need real time updates
user space is probably better.

-Andi


  reply	other threads:[~2004-05-28 22:54 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 22:05 CONFIG_IRQBALANCE for AMD64? Nakajima, Jun
2004-05-28 22:54 ` Andi Kleen [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2004-05-28 23:37 Nakajima, Jun
     [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-28 17:09 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
2004-05-28 21:45             ` Jeff Garzik
2004-05-28 20:03         ` 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=20040528225426.GA89095@colin2.muc.de \
    --to=ak@muc.de \
    --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