From: Andrew Morton <akpm@digeo.com>
To: "Philippe Gramoullé" <philippe.gramoulle@mmania.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.67-mm4 & IRQ balancing
Date: Sat, 19 Apr 2003 13:38:37 -0700 [thread overview]
Message-ID: <20030419133837.0118907b.akpm@digeo.com> (raw)
In-Reply-To: <20030419153923.6d63e22b.philippe.gramoulle@mmania.com>
Philippe Gramoullé <philippe.gramoulle@mmania.com> wrote:
>
> [ SMP IRQ distribution ]
>
> Is this what you are looking for ? and are the values changes meaningful ?
Looks good to me. But it didn't affect your machine at all, did it?
This stuff only counts when the machine is doing a lot of work. The current
IRQ balancer works well under high interrupt frequencies, but does quite the
wrong thing if you're doing a lot of softirq work at low interrupt
frequencies (gige routing with NAPI).
My gut feel is that we'll never get this right with a single in-kernel IRQ
balancer. So the proposal is to pull the IRQ balancer out altogether and to
then merge Arjan's userspace balancer into the main kernel tree.
It's a little radical to go placing userspace daemons into the kernel tree,
but I think it is appropriate - this thing is very tightly coupled to the
kernel.
The proposal has these advantages:
- No version skew problems: if the format of /proc/interrupts changes, we
patch the irq balance daemon at the same time.
- Can build irqbalanced into the intial initramfs image as part of kernel
build. (lacking klibc, we would need to statically link against glibc)
- Doing it in userspace means that we can do more things.
- The balancer can "know about" the differences between NICs, disk
controllers, etc.
- The balancer can be controlled by config files: "I am a router"
- The balancer can support non-x86 architectures
Anyway, that's the theory. None of it has been done yet.
next prev parent reply other threads:[~2003-04-19 20:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 23:58 Philippe Gramoullé
2003-04-19 0:51 ` Andrew Morton
2003-04-19 13:39 ` Philippe Gramoullé
2003-04-19 20:38 ` Andrew Morton [this message]
2003-04-22 10:06 ` Philippe Gramoullé
2003-04-22 10:32 ` Arjan van de Ven
2003-04-23 19:41 ` Bill Davidsen
2003-04-23 20:13 ` Zwane Mwaikambo
2003-04-24 21:32 ` Bill Davidsen
2003-04-25 9:03 ` Arjan van de Ven
2003-04-23 20:15 ` Andrew Morton
2003-04-19 1:03 Nakajima, Jun
2003-04-19 12:21 Chuck Ebbert
2003-04-19 13:14 ` Philippe Gramoullé
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=20030419133837.0118907b.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philippe.gramoulle@mmania.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
all inboxes | Powered by JetHome®