From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Aman Singh <aman.deep.singh@intel.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Chenbo Xia <chenbox@nvidia.com>
Subject: Re: [PATCH 1/1] ethdev: add link speed 800G
Date: Tue, 12 Aug 2025 08:34:31 -0700 [thread overview]
Message-ID: <20250812083431.6502e587@hermes.local> (raw)
In-Reply-To: <20250812144249.316120-1-thomas@monjalon.net>
On Tue, 12 Aug 2025 16:42:48 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:
> diff --git a/lib/ethdev/rte_ethdev.h b/lib/ethdev/rte_ethdev.h
> index 5d7fc5ee9d..d23c143eed 100644
> --- a/lib/ethdev/rte_ethdev.h
> +++ b/lib/ethdev/rte_ethdev.h
> @@ -306,6 +306,7 @@ struct rte_eth_stats {
> #define RTE_ETH_LINK_SPEED_100G RTE_BIT32(14) /**< 100 Gbps */
> #define RTE_ETH_LINK_SPEED_200G RTE_BIT32(15) /**< 200 Gbps */
> #define RTE_ETH_LINK_SPEED_400G RTE_BIT32(16) /**< 400 Gbps */
> +#define RTE_ETH_LINK_SPEED_800G RTE_BIT32(17) /**< 800 Gbps */
Do you want to go further, looking around I see roadmaps for.
1.6Tbs, 3.2 Tbs, 6.4 Tbs (2028) and beyond.
Looks like will run out of bits in 2040...
next prev parent reply other threads:[~2025-08-12 15:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 14:42 Thomas Monjalon
2025-08-12 15:34 ` Stephen Hemminger [this message]
2025-08-13 10:01 ` Thomas Monjalon
2025-08-13 14:18 ` Stephen Hemminger
2025-08-13 15:37 ` Thomas Monjalon
2025-08-12 18:18 ` Andrew Rybchenko
2025-08-12 20:07 ` Morten Brørup
2025-08-13 0:26 ` Khadem Ullah
2025-08-13 0:45 ` fengchengwen
2025-08-13 15:21 ` 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=20250812083431.6502e587@hermes.local \
--to=stephen@networkplumber.org \
--cc=aman.deep.singh@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=thomas@monjalon.net \
/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).