netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: netdev@vger.kernel.org, jgarzik@redhat.com,
	linux-net-drivers@solarflare.com
Subject: Re: [RFC] [PATCH] ethtool: Flags for fibre speed switching
Date: Tue, 22 Jun 2010 10:17:44 -0700 (PDT)	[thread overview]
Message-ID: <20100622.101744.70185793.davem@davemloft.net> (raw)
In-Reply-To: <1276543562.2074.41.camel@achroite.uk.solarflarecom.com>

From: Ben Hutchings <bhutchings@solarflare.com>
Date: Mon, 14 Jun 2010 20:26:02 +0100

> ethtool.h currently defines only SUPPORTED_FIBRE to cover all fibre
> modes.  However, SFP+ slots support both 1G and 10G fibre modules and
> some modules are dual-speed.  Some drivers use the BASE-T flags for SFP+
> modules of all media types, but this is strictly incorrect and can be
> confusing as there are real BASE-T modules for SFP+.  There should be
> distinct flags for fibre modes.  However I'm not sure whether it's worth
> defining flags for each fibre mode (there are quite a few) or only for
> each speed.
> 
> Similarly there is only ADVERTISED_FIBRE to cover all fibre modes.
> Although there is no AN protocol for fibre, an SFP+ NIC effectively
> autonegotiates its speed with the module.  By default, an SFP+ NIC will
> accept both 1G and 10G modules and switch speed automatically.  With a
> dual-speed module, the NIC driver can allow forcing the speed through
> ethtool, but unless it maintains some hidden state it must reset the
> speed whenever the module is hotplugged (perhaps accidentally).  So it
> should be possible for the administrator to control speed selection in a
> sticky way through the advertising mask.

I'm fine with this, feel free to make a formal submission for
net-next-2.6

      reply	other threads:[~2010-06-22 17:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-14 19:26 [RFC] [PATCH] ethtool: Flags for fibre speed switching Ben Hutchings
2010-06-22 17:17 ` David Miller [this message]

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=20100622.101744.70185793.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bhutchings@solarflare.com \
    --cc=jgarzik@redhat.com \
    --cc=linux-net-drivers@solarflare.com \
    --cc=netdev@vger.kernel.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).