From: davem@davemloft.net (David Miller)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2 net-next] net: fec: add napi support to improve proformance
Date: Wed, 23 Jan 2013 02:52:40 -0500 (EST) [thread overview]
Message-ID: <20130123.025240.1835436694088754169.davem@davemloft.net> (raw)
In-Reply-To: <CAHrpEqQ3-prqJaCmt1hfOr4GzDVyuRNvko1SCyQZHdALhHkhkw@mail.gmail.com>
NAPI should not be configurable, all device drivers should be NAPI
only.
next prev parent reply other threads:[~2013-01-23 7:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 4:12 [PATCH 1/2 net-next] net: fec: add napi support to improve proformance Frank Li
2013-01-23 6:21 ` Eric Dumazet
2013-01-23 7:37 ` Frank Li
2013-01-23 13:49 ` Eric Dumazet
2013-01-24 2:26 ` Frank Li
2013-01-24 6:39 ` Waskiewicz Jr, Peter P
2013-01-23 6:37 ` Waskiewicz Jr, Peter P
2013-01-23 7:56 ` Frank Li
2013-01-23 7:26 ` Sascha Hauer
2013-01-23 7:44 ` Frank Li
2013-01-23 7:52 ` David Miller [this message]
2013-01-23 7:53 ` Sascha Hauer
2013-01-23 8:00 ` Frank Li
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=20130123.025240.1835436694088754169.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.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).