From: jamal <hadi@cyberus.ca>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, shemminger@linux-foundation.org,
jgarzik@pobox.com, rusty@rustcorp.com.au
Subject: Re: [PATCH RFC]: napi_struct V5
Date: Tue, 07 Aug 2007 08:52:35 -0400 [thread overview]
Message-ID: <1186491155.5163.68.camel@localhost> (raw)
In-Reply-To: <20070805.232423.21363072.davem@davemloft.net>
On Sun, 2007-05-08 at 23:24 -0700, David Miller wrote:
>
> 3) Attempt to bring NAPI howto as uptodate as is possible for such
> a rotting document. :)
That doc is out of date on the split of work - it focusses mostly
describing the original tulip which did not mix rx and tx in the
napi_poll(). AFAIK, no driver does that today (although i really liked
that scheme, there is a lot of fscked hardware out there that wont work
well with that scheme). Where are the firemen when you need them?
Scanning your changes on the drivers for hardware i possess, I dont see
any issues.
cheers,
jamal
next prev parent reply other threads:[~2007-08-07 12:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 6:24 [PATCH RFC]: napi_struct V5 David Miller
2007-08-06 18:00 ` Michael Chan
2007-08-06 20:50 ` David Miller
2007-08-07 12:52 ` jamal [this message]
2007-08-08 0:59 ` David Miller
2007-08-08 12:10 ` jamal
2007-08-09 4:35 ` David Miller
2007-08-07 22:37 ` Roland Dreier
2007-08-07 23:06 ` David Miller
2007-08-08 3:56 ` Roland Dreier
2007-08-08 4:08 ` David Miller
[not found] ` <OFA2F18805.38AA0BD0-ON87257331.005367FB-88257331.0027BEED@us.ibm.com>
2007-08-08 15:32 ` jamal
2007-08-09 4:23 ` David Miller
2007-08-09 5:32 ` Jeff Garzik
2007-08-09 16:58 ` Roland Dreier
2007-08-10 13:55 ` jamal
2007-08-10 21:39 ` David Miller
2007-08-13 21:47 ` Roland Dreier
2007-08-08 22:20 ` David Miller
2007-08-08 23:23 ` Shirley Ma
2007-08-09 17:49 ` Roland Dreier
2007-08-09 18:16 ` Shirley Ma
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=1186491155.5163.68.camel@localhost \
--to=hadi@cyberus.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.