From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd: add support for forced ethernet speed
Date: Fri, 5 Mar 2021 16:53:46 +0000 [thread overview]
Message-ID: <590c4af0-9650-3ccc-c758-51c434bb8f1e@intel.com> (raw)
In-Reply-To: <20210305041701.40101-1-ajit.khaparde@broadcom.com>
On 3/5/2021 4:17 AM, Ajit Khaparde wrote:
> Add support for forced ethernet speed setting.
> Currently testpmd tries to configure the Ethernet port in autoneg mode.
> It is not possible to set the Ethernet port to a specific speed while
> starting testpmd. In some cases capability to configure a forced speed
> for the Ethernet port during initialization may be necessary. This patch
> tries to add this support.
>
> The patch assumes full duplex setting and does not attempt to change that.
> So speeds like 10M, 100M are not configurable using this method.
>
> The command line to configure a forced speed of 10G:
> dpdk-testpmd -c 0xff -- -i --eth-link-speed 10000
>
> The command line to configure a forced speed of 50G:
> dpdk-testpmd -c 0xff -- -i --eth-link-speed 50000
>
> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
<...>
> @@ -536,3 +536,19 @@ The command line options are:
> bit 1 - two hairpin ports paired
> bit 0 - two hairpin ports loop
> The default value is 0. Hairpin will use single port mode and implicit Tx flow mode.
> +
> +* ``--eth-link-speed``
> +
> + Set a forced link speed to the ethernet port.
> + 1000 - 1Gbps
> + 10000 - 10Gbps
> + 25000 - 25Gbps
> + 40000 - 40Gbps
> + 50000 - 50Gbps
> + 100000 - 100Gbps
> + 200000 - 200Gbps
> + ...
> +
Line breaks are lost when converted to html, it becomes single line, '::' and
indentation is required.
Except from documentation, looks good to me.
next prev parent reply other threads:[~2021-03-05 16:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 19:18 [dpdk-dev] [PATCH] " Ajit Khaparde
2021-02-25 18:25 ` Ferruh Yigit
2021-02-26 6:43 ` Andrew Rybchenko
2021-02-26 11:21 ` Ferruh Yigit
2021-02-26 16:18 ` Andrew Boyer
2021-03-01 12:20 ` Ferruh Yigit
2021-03-01 4:47 ` Ajit Khaparde
2021-03-12 8:45 ` Ferruh Yigit
2021-03-05 4:15 ` Ajit Khaparde
2021-03-05 4:17 ` [dpdk-dev] [PATCH v2] " Ajit Khaparde
2021-03-05 16:53 ` Ferruh Yigit [this message]
2021-03-05 19:42 ` [dpdk-dev] [PATCH v3] " Ajit Khaparde
2021-03-08 11:03 ` Ferruh Yigit
2021-02-25 18:33 ` [dpdk-dev] [PATCH] " Andrew Boyer
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=590c4af0-9650-3ccc-c758-51c434bb8f1e@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.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).