From: Andrew Morton <akpm@zip.com.au>
To: Dave Larson <davlarso@acm.org>
Cc: linux-kernel@vger.kernel.org, tsbogend@alpha.franken.de
Subject: Re: Is this a bug in TCP or the PCNet32 driver?
Date: Tue, 12 Feb 2002 12:12:14 -0800 [thread overview]
Message-ID: <3C69771E.17F26646@zip.com.au> (raw)
In-Reply-To: <Pine.GSO.4.31.0202120728000.24018-100000@linus.davelarson.net>
Dave Larson wrote:
>
> The way things are today, the TCP code rely on the hardware drivers to
> free an skb as soon as it is transmitted. But in that case of PCNet32,
> that doesn't happen. On the other hand, PCNet32 does seem reasonable in
> it's attempts to reduce the number of interrupts, although that breaks the
> tcp code in this case were these isn't much network activity.
>
Yup. Tx interrupt mitigation like this is a really neat feature. It
can make a huge improvement in performance. But the driver does need
to implement a timer to fix the problem which you have described.
-
next prev parent reply other threads:[~2002-02-12 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-12 14:05 Is this a bug in TCP or the PCNet32 driver? Dave Larson
2002-02-12 20:12 ` Andrew Morton [this message]
2002-02-13 5:04 ` David S. 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=3C69771E.17F26646@zip.com.au \
--to=akpm@zip.com.au \
--cc=davlarso@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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