From: Jeff Garzik <jgarzik@pobox.com>
To: smarchetto1@tin.it
Cc: linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: NAPI on 8139too
Date: Thu, 28 Aug 2003 17:01:03 -0400 [thread overview]
Message-ID: <3F4E6D8F.6070003@pobox.com> (raw)
In-Reply-To: <1062094999.3149.33.camel@localhost>
Michele 'mydecay' Marchetto wrote:
> I was wondering why NAPI hasn't been ported on 8139too yet..
I think it would be a good idea. You can stuff a lot of 68-byte packets
into a 32K or 64K contiguous buffer. Jes Sorensen wrote a patch a while
ago that sampling the incoming rate, and backed off if the rate was too
high -- basically a poor man's NAPI.
So, volunteers? Just convert the RX path to NAPI, not all interrupt events.
Jeff
parent reply other threads:[~2003-08-28 21:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1062094999.3149.33.camel@localhost>]
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=3F4E6D8F.6070003@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=smarchetto1@tin.it \
/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.