From: "Nakajima, Jun" <jun.nakajima@intel.com>
To: "Christoph Hellwig" <hch@infradead.org>,
"Kamble, Nitin A" <nitin.a.kamble@intel.com>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>,
"Saxena, Sunil" <sunil.saxena@intel.com>,
"Mallick, Asit K" <asit.k.mallick@intel.com>
Subject: RE: KIRQ Balance
Date: Sat, 11 Jan 2003 08:54:21 -0800 [thread overview]
Message-ID: <3014AAAC8E0930438FD38EBF6DCEB5647D0F7B@fmsmsx407.fm.intel.com> (raw)
This is the one we posted (by Nitin) recently. It's a complementary solution to Ingo's random/round-robin interrupt routing, co-existing with it. See Nitin's emails for the patch and details.
Jun
> -----Original Message-----
> From: Christoph Hellwig [mailto:hch@infradead.org]
> Sent: Saturday, January 11, 2003 2:32 AM
> To: Kamble, Nitin A
> Cc: Linux Kernel
> Subject: Re: KIRQ Balance
>
> On Mon, Jan 06, 2003 at 11:40:31AM -0800, Kamble, Nitin A wrote:
> > Hi Martin,
> > Would somebody get a chance to try the kirq patch out? If yes, please
> > let me know, how the patch did on your systems. Did your guys find any
> > issues with it? I will also appreciate more comments.
>
> Where/What is the kirq patch?
>
> -
> 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/
next reply other threads:[~2003-01-11 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 16:54 Nakajima, Jun [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-06 19:40 Kamble, Nitin A
2003-01-11 10:31 ` Christoph Hellwig
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=3014AAAC8E0930438FD38EBF6DCEB5647D0F7B@fmsmsx407.fm.intel.com \
--to=jun.nakajima@intel.com \
--cc=asit.k.mallick@intel.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®