From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Jeff Garzik <jgarzik@pobox.com>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: ncunningham@cyclades.com, kwijibo@zianet.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Should kirqd work on HT?
Date: Sun, 20 Feb 2005 06:44:12 -0800 [thread overview]
Message-ID: <320350000.1108910651@[10.10.2.4]> (raw)
In-Reply-To: <421769BD.4060606@pobox.com>
--Jeff Garzik <jgarzik@pobox.com> wrote (on Saturday, February 19, 2005 11:30:53 -0500):
> Pallipadi, Venkatesh wrote:
>> You are right. Kernel balancer doesn't move around the irqs, unless it
>> has too many interrupts. The logic is moving around interrupts all the
>> time will not be good on caches. So, there is a threshold above which
>> the balancer start moving things around.
>>
>> You should see them moving around if you do 'ping -f' or a big 'dd' from
>> the disk.
>
> If kirqd is moving NIC interrupts, it's broken.
>
> (and another reason why irqbalanced is preferable)
Why is it broken to move NIC interrupts? Obviously you don't want to
rotate them around a lot, but in the interests of fairness to other
processes, it seems reasonable to migrate them occasionally (IIRC, kirqd
rate limits to once a second or something).
M.
next prev parent reply other threads:[~2005-02-20 14:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-19 13:30 Should kirqd work on HT? Pallipadi, Venkatesh
2005-02-19 16:30 ` Jeff Garzik
2005-02-20 14:44 ` Martin J. Bligh [this message]
2005-02-21 1:08 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-02-19 6:31 Nigel Cunningham
2005-02-19 6:44 ` Kwijibo
2005-02-19 9:02 ` Nigel Cunningham
2005-02-19 9:36 ` Arjan van de Ven
2005-02-19 6:52 ` Jeff Garzik
2005-02-19 9:07 ` Nigel Cunningham
2005-02-19 9:36 ` Arjan van de Ven
2005-02-19 10:54 ` Nigel Cunningham
2005-02-19 10:58 ` Nigel Cunningham
2005-02-19 11:49 ` Arjan van de Ven
2005-02-20 14:45 ` 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='320350000.1108910651@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=jgarzik@pobox.com \
--cc=kwijibo@zianet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@cyclades.com \
--cc=venkatesh.pallipadi@intel.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;
as well as URLs for NNTP newsgroup(s).