From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: joe@perches.com, therbert@google.com, netdev@vger.kernel.org,
aabdulla@nvidia.com
Subject: Re: [PATCH] forcedeth: Stay in NAPI as long as there's work
Date: Wed, 28 Apr 2010 14:25:34 -0700 (PDT) [thread overview]
Message-ID: <20100428.142534.57451492.davem@davemloft.net> (raw)
In-Reply-To: <20100428112528.01277670@nehalam>
From: Stephen Hemminger <shemminger@vyatta.com>
Date: Wed, 28 Apr 2010 11:25:28 -0700
> The following does the same thing without the extra overhead
> of testing all the registers. It also handles the out of memory
> case.
>
> Compile tested only...
>
> Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
Tom can you test this version?
next prev parent reply other threads:[~2010-04-28 21:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 6:36 [PATCH] forcedeth: Stay in NAPI as long as there's work Tom Herbert
2010-04-28 17:54 ` Joe Perches
2010-04-28 18:07 ` Tom Herbert
2010-04-28 18:18 ` Tom Herbert
2010-04-28 18:13 ` Stephen Hemminger
2010-04-28 18:25 ` Stephen Hemminger
2010-04-28 21:25 ` David Miller [this message]
2010-04-28 23:56 ` Tom Herbert
2010-04-30 23:17 ` David Miller
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=20100428.142534.57451492.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aabdulla@nvidia.com \
--cc=joe@perches.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=therbert@google.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).