From: Arjan van de Ven <arjan@linux.intel.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Auke Kok <auke-jan.h.kok@intel.com>,
linux-kernel@vger.kernel.org, jesse.brandeburg@intel.com,
john.ronciak@intel.com, netdev@vger.kernel.org
Subject: Re: [RFC] irqbalance: Mark in-kernel irqbalance as obsolete, set to N by default
Date: Fri, 04 Aug 2006 07:36:06 -0700 [thread overview]
Message-ID: <44D35B56.6060500@linux.intel.com> (raw)
In-Reply-To: <20060803194550.9ff31bc1.akpm@osdl.org>
Andrew Morton wrote:
> On Mon, 31 Jul 2006 10:35:26 -0700
> Auke Kok <auke-jan.h.kok@intel.com> wrote:
>
>> We've recently seen a number of user bug reports against e1000 that the
>> in-kernel irqbalance code is detrimental to network latency. The algorithm
>> keeps swapping irq's for NICs from cpu to cpu causing extremely high network
>> latency (>1000ms).
>
> What kernel versions? Some IRQ balancer fixes went in shortly after 2.6.17.
>
> It would be better if poss to fix the balancer rather than deprecating it.
to some degree the in kernel balancer cannot really make the level of decisions that a
userspace balancer can make, at least not without making all kernel developers vomit ;)
(for example the userspace balancer looks in /proc/interrupts and parses that to see
which interrupts are used by networking versus which by storage etc, and has different
balancing policies for those and other classes; the networking policy basically comes down to
"pin the interrupt unless some higher networking interrupt really gets in the way")
next prev parent reply other threads:[~2006-08-04 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 17:35 [RFC] irqbalance: Mark in-kernel irqbalance as obsolete, set to N by default Auke Kok
2006-08-04 2:45 ` Andrew Morton
2006-08-04 14:25 ` Auke Kok
2006-08-04 14:36 ` Arjan van de Ven [this message]
[not found] <6EJUl-4br-13@gated-at.bofh.it>
[not found] ` <6FXVd-1Gl-11@gated-at.bofh.it>
[not found] ` <6G9jL-1Yg-41@gated-at.bofh.it>
2006-08-04 21:48 ` Bodo Eggert
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=44D35B56.6060500@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=akpm@osdl.org \
--cc=auke-jan.h.kok@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).