RE: [PATCH][IO_APIC] 2.5.63bk7 irq_balance improvments / bug-fixes

Nakajima, Jun (jun.nakajima@intel.com)
Thu, 6 Mar 2003 12:01:45 -0800


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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/