From: "Kamble, Nitin A" <nitin.a.kamble@intel.com>
To: "Andrew Morton" <akpm@digeo.com>
Cc: <linux-kernel@vger.kernel.org>, <kai.bankett@ontika.net>,
<mingo@redhat.com>, "Nakajima, Jun" <jun.nakajima@intel.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: Tue, 4 Mar 2003 20:21:10 -0800 [thread overview]
Message-ID: <E88224AA79D2744187E7854CA8D9131DA8B7E0@fmsmsx407.fm.intel.com> (raw)
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.
There is some information which is only available in the kernel today,
Also the future implementation might need more kernel data. This is
important for interfaces such as NAPI, where interrupts handling changes
on the fly.
Thanks,
Nitin
> Now there has been some discssion as to whether these algorithmic
> decisions
> can be moved out of the kernel altogether. And with periods of one
and
> five
> seconds that does appear to be feasible.
>
> I believe that you have looked at this before and encountered some
problem
> with it. Could you please describe what happened there?
next reply other threads:[~2003-03-05 4:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 4:21 Kamble, Nitin A [this message]
2003-03-05 4:38 ` [PATCH][IO_APIC] 2.5.63bk7 irq_balance improvments / bug-fixes Jeff Garzik
2003-03-05 15:46 ` Jason Lunz
2003-03-05 18:26 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2003-03-06 20:01 Nakajima, Jun
2003-03-05 19:57 Kamble, Nitin A
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=E88224AA79D2744187E7854CA8D9131DA8B7E0@fmsmsx407.fm.intel.com \
--to=nitin.a.kamble@intel.com \
--cc=akpm@digeo.com \
--cc=asit.k.mallick@intel.com \
--cc=jun.nakajima@intel.com \
--cc=kai.bankett@ontika.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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).