Netdev List
 help / color / mirror / Atom feed
From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: "D H, Siddaraju" <siddaraju.dh@intel.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "Das, Shubham" <shubham.das@intel.com>,
	"Chintalapalle, Balaji" <balaji.chintalapalle@intel.com>,
	"Srinivasan, Vijay" <vijay.srinivasan@intel.com>
Subject: Re: the confusing 10000base_CR. Shouldn't it be 10000_SFI_DA?
Date: Fri, 26 Jun 2026 16:33:54 +0200	[thread overview]
Message-ID: <9527a821-114a-4696-925c-1529da2bf5b8@bootlin.com> (raw)
In-Reply-To: <MW4PR11MB6912A234CAAAFD25EAC7C8909AEB2@MW4PR11MB6912.namprd11.prod.outlook.com>

Hi,

On 6/26/26 16:15, D H, Siddaraju wrote:
> Hi Linux Ethernet Team,
> 
> We explored Ethtool's "10000base_CR" PMD PHY type
> and we think it might be just a wrong name.
> 
> Why we called 10000Base_CR, a confusing name?
> Because it fails all below 4 major highlights of a "typical base-CR"
>     1. Every other Base-CR is an IEEE defined PMD specs
>     2. All Base-CR have AN LT (Auto-Negotiation & Link Training)
>     3. Almost all CR have FEC mandatory
>     4. IEEE CR is a very close sibling of IEEE KR, the complex ones
> 
> There is NO IEEE 802.3 or ANY other standard spec to
> support 10000base-CR and the industry fully adopted
> SFF-8431 Appendix-E Direct Attach cable as 10G-SFI-DA.
> 
> We feel 10000Base_CR must be renamed to 10000_SFI_DA.
>     SFI: SFP+ high speed serial electrical interface
>     DA: Direct Attach cable media

Well it's too late for a rename, this is part of the userspace API
so this name is here to stay :

https://elixir.bootlin.com/linux/v7.1.1/source/include/uapi/linux/ethtool.h#L2013

This was introduced in 2016, I think we won't gain much by adding
another linkmode that's equivalent. Even if this isn't strictly
speaking the correct mode, even some vendors sell their DA cable
as 10GBaseCR cables now :/

Maxime


      parent reply	other threads:[~2026-06-26 14:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26 14:15 the confusing 10000base_CR. Shouldn't it be 10000_SFI_DA? D H, Siddaraju
2026-06-26 14:32 ` Andrew Lunn
2026-06-26 18:12   ` D H, Siddaraju
2026-06-26 18:18     ` Andrew Lunn
2026-06-26 19:19       ` D H, Siddaraju
2026-06-29  9:30         ` Maxime Chevallier
2026-06-29 11:25           ` D H, Siddaraju
2026-06-29 13:11             ` Andrew Lunn
2026-06-29 17:29               ` D H, Siddaraju
2026-06-29 18:14           ` Michal Kubecek
2026-07-02 14:54             ` D H, Siddaraju
2026-06-26 14:33 ` Maxime Chevallier [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=9527a821-114a-4696-925c-1529da2bf5b8@bootlin.com \
    --to=maxime.chevallier@bootlin.com \
    --cc=balaji.chintalapalle@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=shubham.das@intel.com \
    --cc=siddaraju.dh@intel.com \
    --cc=vijay.srinivasan@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox