From: "Quan Sun" <cfk.quan@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Different scheduler behavior between 2.4 and 2.6
Date: Thu, 10 May 2007 13:46:53 +0800 [thread overview]
Message-ID: <e810d8480705092246k1bb9afe6ma253fd7679f5031a@mail.gmail.com> (raw)
Hi,
Recently I met a problem on different scheduler behavior between
2.4.22 and 2.6.18.8.
The application works as a proxy, it listen on an interface,
connect through another interface. This application works on a box
with two Xeon cpu, each of them is hyper-threading.
On 2.4.22, CPU0 serve interrupts, the application works on other
three CPUs.
But on 2.6.18.8, if I turn on 'noirqbalance' kernel parameter, and no
irqbalance process, the application will stuck to CPU0 as well as interrupts
after several seconds' working. Then there will be a 0% idle cpu, and
three 100%idle CPUs.
/proc/interrupt shows all eths's interrupts are working at CPU0.
It seems that scheduler ignores the working load of interrupts.
My question is, is there a way to tune 2.6 kernel working as 2.4?
Just one cpu for interrupts, other three cpu for normal work.
--
Quan Sun
reply other threads:[~2007-05-10 5:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e810d8480705092246k1bb9afe6ma253fd7679f5031a@mail.gmail.com \
--to=cfk.quan@gmail.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
all inboxes | Powered by JetHome®