From: Marc Herbert <marc.herbert@free.fr>
To: netdev@oss.sgi.com
Cc: Roger Luethi <rl@hellgate.ch>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] ethtool semantics
Date: Tue, 8 Jun 2004 01:43:26 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0406080111550.2832@fcat> (raw)
In-Reply-To: <20040607145723.41da5783.davem@redhat.com>
On Mon, 7 Jun 2004, David S. Miller wrote:
> On Mon, 7 Jun 2004 23:28:04 +0200
> Roger Luethi <rl@hellgate.ch> wrote:
>
> > What is the correct response if a user passes ethtool speed or duplex
> > arguments while autoneg is on? Some possible answers are:
> >
> > a) Yell at the user for doing something stupid.
> >
> > b) Fail silently (i.e. ignore command).
> >
> > c) Change advertised value accordingly and initiate new negotiation.
> >
> > d) Consider "autoneg off" implied, force media accordingly.
> >
> > The ethtool(8) man page I'm looking at doesn't address that question. The
> > actual behavior I've seen is b) which is by far my least preferred
> > solution.
> speed and duplex fields should be silently ignored in this case
I find the c) feature very convenient. For instance it allows reliably
downgrading a link connected to a switch without having to fiddle with
the configuration of the switch, something which is usually (pick your
favourites) non-standard, painful, not authorized, not implemented,
buggy,...
Command line parameters of the bcm5700 driver do implement c) (among
other nifties). Documented in its man page. Command line parameters of
e1000 also allow some control over the autonegociation process, even
if not using c) but a different (and less user-friendly) syntax. See
Documentation/--/e1000.txt. From David's words, I suspect this feature
is simply missing from ethtool.
Finally, silently ignoring user input is not very user-friendly IMHO.
I would much prefer a) to b).
I am aware that my preferences are probably in inverse order of the
amount of work required.
PS: I read netdev but not linux-kernel
next prev parent reply other threads:[~2004-06-07 23:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 21:28 [RFC] ethtool semantics Roger Luethi
2004-06-07 21:57 ` David S. Miller
2004-06-07 23:43 ` Marc Herbert [this message]
2004-06-08 21:08 ` Roger Luethi
2004-06-09 21:09 ` Bill Davidsen
2004-06-09 21:38 ` Roger Luethi
2004-06-09 22:12 ` David S. Miller
2004-06-14 13:11 ` Marc Herbert
2004-06-14 17:01 ` Tim Hockin
2004-06-14 19:32 ` Marc Herbert
2004-06-14 19:42 ` Roger Luethi
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=Pine.LNX.4.58.0406080111550.2832@fcat \
--to=marc.herbert@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=rl@hellgate.ch \
/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).