From: Jamie Lokier <jamie@shareable.org>
To: Kai Bankett <kbankett@aol.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] irq_balance does not make sense with HT but single physical CPU
Date: Wed, 26 Nov 2003 18:40:31 +0000 [thread overview]
Message-ID: <20031126184031.GC14383@mail.shareable.org> (raw)
In-Reply-To: <3FC4B5C8.6020405@aol.com>
Kai Bankett wrote:
> this patch should disable irq_balance threat in case of only one
> installed physical cpu thats running in HyperThreading-mode (so reported
> as 2 cpus).
> I think it should make no sense to run irq_blanance in that special case
> - please correct me if i´m wrong.
Does it makes no sense?
If you had two tasks both running continuously, one per sibling, then
not IRQ balancing will penalise the task on the sibling which is
getting most interrupts.
-- Jamie
next prev parent reply other threads:[~2003-11-26 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 14:16 [PATCH] irq_balance does not make sense with HT but single physical CPU Kai Bankett
2003-11-26 15:46 ` Zwane Mwaikambo
2003-11-26 16:32 ` Kai Bankett
2003-11-26 17:09 ` Zwane Mwaikambo
2003-11-26 18:40 ` Jamie Lokier [this message]
2003-11-27 8:48 ` Kai Bankett
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=20031126184031.GC14383@mail.shareable.org \
--to=jamie@shareable.org \
--cc=kbankett@aol.com \
--cc=linux-kernel@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