From: Jeff Garzik <jgarzik@pobox.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] sky2: flow control off
Date: Tue, 06 Feb 2007 19:18:07 -0500 [thread overview]
Message-ID: <45C91ABF.9030504@pobox.com> (raw)
In-Reply-To: <20070202153425.2d979fd4@freekitty>
Stephen Hemminger wrote:
> Turn flow control off for sky2. When flow control is on, the transmitter
> may get randomly stuck. Perhaps there is hardware problem, but until
> Marvell provides errata information for workaround, it should default to off.
>
> Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org>
> ---
> drivers/net/sky2.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/sky2.c b/drivers/net/sky2.c
> index 822dd0b..a31dea5 100644
> --- a/drivers/net/sky2.c
> +++ b/drivers/net/sky2.c
> @@ -3263,7 +3263,7 @@ #endif
>
> /* Auto speed and flow control */
> sky2->autoneg = AUTONEG_ENABLE;
> - sky2->flow_mode = FC_BOTH;
> + sky2->flow_mode = FC_NONE;
I ACK the patch... conditional on some -mm style testing and user ACKs.
Logic: if there were no downsides to disabling flow control globally,
the world's networks would have already done so. Flow control can be
quite helpful, so I while I understand the errata argument, I also want
to understand the full effect of this tiny patch.
Jeff
next prev parent reply other threads:[~2007-02-07 0:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 23:34 [PATCH] sky2: flow control off Stephen Hemminger
2007-02-03 22:32 ` Willy Tarreau
2007-02-05 17:22 ` Stephen Hemminger
2007-02-05 18:42 ` Willy Tarreau
2007-02-07 0:18 ` Jeff Garzik [this message]
2007-02-07 3:57 ` Stephen Hemminger
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=45C91ABF.9030504@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=torvalds@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 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).