From: Andi Kleen <andi@firstfloor.org>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: Andi Kleen <andi@firstfloor.org>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, rusty@rustcorp.com.au, jgarzik@pobox.com
Subject: Re: [PATCH]: Resurrect napi_poll patch.
Date: Mon, 23 Jul 2007 19:06:42 +0200 [thread overview]
Message-ID: <20070723170642.GA13771@one.firstfloor.org> (raw)
In-Reply-To: <20070723105822.3a9fa152@oldman.hamilton.local>
On Mon, Jul 23, 2007 at 10:58:22AM +0100, Stephen Hemminger wrote:
> On 21 Jul 2007 15:26:00 +0200
> Andi Kleen <andi@firstfloor.org> wrote:
>
> > David Miller <davem@davemloft.net> writes:
> > >
> > > Good candidates for taking advantage of multi-napi are:
> > >
> > > 1) e1000
> > > 2) ucc_geth
> > > 3) ehea
> > > 4) sunvnet
> >
> > s2io.c
>
> sky2.c could use it because of issues with dual-port that share
> one napi for status.
Sorry, I didn't parse the sentence. Did you mean "couldn't use it" ...?
Also can you elaborate why it shouldn't work?
-Andi
next prev parent reply other threads:[~2007-07-23 17:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 5:31 [PATCH]: Resurrect napi_poll patch David Miller
2007-07-21 5:46 ` Patrick McHardy
2007-07-21 6:00 ` David Miller
2007-07-21 7:14 ` Rusty Russell
2007-07-21 7:42 ` David Miller
2007-07-21 8:00 ` Rusty Russell
2007-07-21 18:54 ` David Miller
2007-07-21 23:10 ` Rusty Russell
2007-07-22 1:59 ` David Miller
2007-07-22 2:39 ` Rusty Russell
2007-07-22 3:54 ` David Miller
2007-07-22 7:18 ` David Miller
2007-07-22 7:36 ` David Miller
2007-07-22 7:51 ` Rusty Russell
2007-07-22 8:24 ` David Miller
2007-07-21 13:26 ` Andi Kleen
2007-07-23 9:58 ` Stephen Hemminger
2007-07-23 17:06 ` Andi Kleen [this message]
2007-07-23 21:14 ` Stephen Hemminger
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=20070723170642.GA13771@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=shemminger@linux-foundation.org \
/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).