All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@amd.com>
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>,
	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: Fri, 17 Feb 2023 00:56:48 +0100	[thread overview]
Message-ID: <10546526.aFP6jjVeTY@thomas> (raw)
In-Reply-To: <6cb5c97c-9a5e-e866-c37d-f7be7fa182bc@amd.com>

16/02/2023 13:30, Ferruh Yigit:
> On 2/16/2023 10:43 AM, 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>
> > ---
> >  app/test-pmd/cmdline.c             | 2 ++
> >  app/test-pmd/config.c              | 2 ++
> >  app/test-pmd/parameters.c          | 3 +++
> >  app/test/test_ethdev_link.c        | 3 ++-
> >  drivers/net/virtio/virtio_ethdev.c | 2 ++
> >  lib/ethdev/rte_ethdev.c            | 6 ++++++
> >  lib/ethdev/rte_ethdev.h            | 2 ++
> >  7 files changed, 19 insertions(+), 1 deletion(-)
> 
> It looks like some testpmd help strings and documentation missed, please
> check previous commit as reference:
> Commit f6eb39384933 ("ethdev: add 200G link speed")
> 
> 
> Also last time release notes also updated for new speed, what about
> doing same?

Yes you're right, I will do the same, thanks.






  reply	other threads:[~2023-02-16 23:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 10:43 [PATCH] ethdev: add link speed 400G Thomas Monjalon
2023-02-16 10:49 ` Morten Brørup
2023-02-16 11:23 ` Andrew Rybchenko
2023-02-16 11:27 ` fengchengwen
2023-02-16 12:30 ` Ferruh Yigit
2023-02-16 23:56   ` Thomas Monjalon [this message]
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=10546526.aFP6jjVeTY@thomas \
    --to=thomas@monjalon.net \
    --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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.