From: "Nakajima, Jun" <jun.nakajima@intel.com>
To: "Arjan van de Ven" <arjan@fenrus.demon.nl>,
"Kamble, Nitin A" <nitin.a.kamble@intel.com>
Cc: "Andrew Morton" <akpm@digeo.com>, <linux-kernel@vger.kernel.org>,
<kai.bankett@ontika.net>, <mingo@redhat.com>,
"Mallick, Asit K" <asit.k.mallick@intel.com>,
"Saxena, Sunil" <sunil.saxena@intel.com>
Subject: RE: [PATCH][IO_APIC] 2.5.63bk7 irq_balance improvments / bug-fixes
Date: Thu, 6 Mar 2003 12:01:45 -0800 [thread overview]
Message-ID: <3014AAAC8E0930438FD38EBF6DCEB5640133881D@fmsmsx407.fm.intel.com> (raw)
I think tuning for NUMA issues are different. The intention/scope of this patch was to provide an efficient interrupt routing in software that would work for dual/SMP P4P based systems. Although we found this improved older systems as well, there was no need to do this earlier since it was done by the chipsets in the platform and software did not have any thing to do.
Jun
> -----Original Message-----
> From: Arjan van de Ven [mailto:arjan@fenrus.demon.nl]
> Sent: Wednesday, March 05, 2003 10:27 AM
> To: Kamble, Nitin A
> Cc: Andrew Morton; linux-kernel@vger.kernel.org; kai.bankett@ontika.net;
> mingo@redhat.com; Nakajima, Jun; Mallick, Asit K; Saxena, Sunil
> Subject: RE: [PATCH][IO_APIC] 2.5.63bk7 irq_balance improvments / bug-
> fixes
>
> On Wed, 2003-03-05 at 05:21, Kamble, Nitin A wrote:
> > There are few issues we found with the user level daemon approach.
> >
> > Static binding compatibility: With the user level daemon, users can
> > not
> > use the /proc/irq/i/smp_affinity interface for the static binding of
> > interrupts.
>
> no they can just write/change the config file, with a gui if needed
>
> >
> > There is some information which is only available in the kernel today,
>
> there's also some information only available to userspace today that the
> userspace daemon can and does use.
>
> > Also the future implementation might need more kernel data. This is
> > important for interfaces such as NAPI, where interrupts handling changes
> > on the fly.
>
> ehm. almost. but napi isn't it ....
>
> and the userspace side can easily have a system vendor provided file
> that represents all kinds of very specific system info about the numa
> structure..... working with every kernel out there.
next reply other threads:[~2003-03-06 19:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 20:01 Nakajima, Jun [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-05 19:57 [PATCH][IO_APIC] 2.5.63bk7 irq_balance improvments / bug-fixes Kamble, Nitin A
2003-03-05 4:21 Kamble, Nitin A
2003-03-05 4:38 ` Jeff Garzik
2003-03-05 15:46 ` Jason Lunz
2003-03-05 18:26 ` Arjan van de Ven
2003-03-04 23:33 Kamble, Nitin A
2003-03-04 23:51 ` Andrew Morton
2003-03-05 10:48 ` Kai Bankett
2003-03-04 16:33 Kai Bankett
2003-03-04 16:45 ` Jeff Garzik
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=3014AAAC8E0930438FD38EBF6DCEB5640133881D@fmsmsx407.fm.intel.com \
--to=jun.nakajima@intel.com \
--cc=akpm@digeo.com \
--cc=arjan@fenrus.demon.nl \
--cc=asit.k.mallick@intel.com \
--cc=kai.bankett@ontika.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nitin.a.kamble@intel.com \
--cc=sunil.saxena@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).