From: fengchengwen <fengchengwen@huawei.com>
To: Thomas Monjalon <thomas@monjalon.net>, <dev@dpdk.org>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
Jerin Jacob <jerinj@marvell.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Raslan Darawsheh <rasland@nvidia.com>,
David Marchand <david.marchand@redhat.com>,
Aman Singh <aman.deep.singh@intel.com>,
Yuying Zhang <yuying.zhang@intel.com>,
Ferruh Yigit <ferruh.yigit@amd.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Chenbo Xia <chenbo.xia@intel.com>
Subject: Re: [PATCH] ethdev: add link speed 400G
Date: Thu, 16 Feb 2023 19:27:57 +0800 [thread overview]
Message-ID: <42504089-306c-2e68-148d-462493b59d8e@huawei.com> (raw)
In-Reply-To: <20230216104350.1639394-1-thomas@monjalon.net>
Hi Thomas,
Higher rates are generally implemented with multiple lanes. The lane configuration is
critical to link negotiation success. The number of lanes configured using the ethtool
is provided [1].
Currently, the community uses only one u32 bit (link_speed) to indicate a rate, which
is not enough.
It is recommended that the rate be extended to support the configuration of the number
of lanes. Our team plan to develop it target 23.07 version (have not yet been designed).
Maybe other team already developping it (if have please let me know so that we can reduce
invest).
Beside, as for this patch, I think we could upstream first.
[1] https://lore.kernel.org/netdev/20201010154119.3537085-1-idosch@idosch.org/T/
On 2023/2/16 18:43, Thomas Monjalon wrote:
> There are some devices supporting 400G speed,
> and it is well standardized in IEEE.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
Acked-by: Chengwen Feng <fengchengwen@huawei.com>
next prev parent reply other threads:[~2023-02-16 11:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 10:43 Thomas Monjalon
2023-02-16 10:49 ` Morten Brørup
2023-02-16 11:23 ` Andrew Rybchenko
2023-02-16 11:27 ` fengchengwen [this message]
2023-02-16 12:30 ` Ferruh Yigit
2023-02-16 23:56 ` Thomas Monjalon
2023-03-01 11:16 ` [PATCH v2] " Thomas Monjalon
2023-03-01 14:50 ` Ajit Khaparde
2023-03-02 8:58 ` Ferruh Yigit
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=42504089-306c-2e68-148d-462493b59d8e@huawei.com \
--to=fengchengwen@huawei.com \
--cc=ajit.khaparde@broadcom.com \
--cc=aman.deep.singh@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--cc=chenbo.xia@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=jerinj@marvell.com \
--cc=maxime.coquelin@redhat.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--cc=yuying.zhang@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;
as well as URLs for NNTP newsgroup(s).