From: Jeff Garzik <jgarzik@pobox.com>
To: Robert Olsson <Robert.Olsson@data.slu.se>
Cc: Andrew Morton <akpm@osdl.org>, netdev@oss.sgi.com, dfages@arkoon.net
Subject: Re: Fw: [BUG/PATCH] CONFIG_NET_HW_FLOWCONTROL and SMP
Date: Mon, 29 Sep 2003 17:39:29 -0400 [thread overview]
Message-ID: <3F78A691.1040406@pobox.com> (raw)
In-Reply-To: <16248.41796.797321.700866@robur.slu.se>
Robert Olsson wrote:
> Hello!
>
> IMO HW_FLOWCONTROL is now outdated. It has served very well and encouraged
> people to use for Linux production networking. With a 2 tulip NIC's on a UP
> system as a typical system. Only tulip has code for it. This option was
> added by Alexey in 2.1.63 something...
If someone had a NAPI patch for tulip, we could remove HW_FLOWCONTROL
option altogether :)
Jeff
next prev parent reply other threads:[~2003-09-29 21:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 19:37 Fw: [BUG/PATCH] CONFIG_NET_HW_FLOWCONTROL and SMP Andrew Morton
2003-09-29 21:25 ` Robert Olsson
2003-09-29 21:39 ` Jeff Garzik [this message]
2003-09-30 14:45 ` Robert Olsson
2003-10-02 15:31 ` Robert Olsson
2003-10-02 17:47 ` Jeff Garzik
2003-10-02 19:34 ` Andrew Morton
2003-10-03 14:10 ` Robert Olsson
2003-09-30 2:17 ` jamal
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=3F78A691.1040406@pobox.com \
--to=jgarzik@pobox.com \
--cc=Robert.Olsson@data.slu.se \
--cc=akpm@osdl.org \
--cc=dfages@arkoon.net \
--cc=netdev@oss.sgi.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 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.