netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Robert Schlabbach <Robert.Schlabbach@gmx.net>
Cc: netdev@vger.kernel.org
Subject: Re: ixgbe: How to do this without a module parameter?
Date: Tue, 26 Oct 2021 02:32:44 +0200	[thread overview]
Message-ID: <YXdMrL2ZEW5c+adB@lunn.ch> (raw)
In-Reply-To: <trinity-b6836216-b49e-4e59-80af-7b9c48918b19-1635205677415@3c-app-gmx-bap12>

> So I realize using ethtool is a viable solution after all and the module
> parameter is not needed. I'd still wish the ixgbe driver would default to full
> functionality and require the users with the "bad" switches in their networks
> to employ ethtool to cripple its function, but I suppose that'd be tough to
> sell to Intel...

Maybe, maybe not. Quoting the above message:

> This is the first time I've heard of anyone asking for 2.5G or 5G
> outside of the telecom space, so we went with the option of changing
> the default.

NBASE-T is no longer just telecom space. It is slowly becoming more
and more popular in general deployment.

At some point, there will be more standard conforming switches than
broken switches, and then it would make sense to enable the higher
speeds by default. Especially when everybody else is doing
NBASE-T. You see a lot of ARM SoCs with such ports, etc.

	 Andrew

  reply	other threads:[~2021-10-26  0:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 20:23 ixgbe: How to do this without a module parameter? Robert Schlabbach
2021-10-25 20:59 ` Toke Høiland-Jørgensen
2021-10-25 21:11   ` Andrew Lunn
2021-10-25 23:47     ` Robert Schlabbach
2021-10-26  0:32       ` Andrew Lunn [this message]
2021-10-26 23:50     ` Aw: " Robert Schlabbach
2021-10-27  0:15       ` Andrew Lunn
2021-10-27 19:12         ` Robert Schlabbach

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=YXdMrL2ZEW5c+adB@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Robert.Schlabbach@gmx.net \
    --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).