From: Andrew Boyer <aboyer@pensando.io>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: add support for forced ethernet speed
Date: Thu, 25 Feb 2021 13:33:10 -0500 [thread overview]
Message-ID: <279CCAC7-AB50-4B2A-A724-C9DF1642A797@pensando.io> (raw)
In-Reply-To: <20210222191824.40230-1-ajit.khaparde@broadcom.com>
> On Feb 22, 2021, at 2:18 PM, Ajit Khaparde <ajit.khaparde@broadcom.com> 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>
> ---
...
> @@ -485,6 +486,41 @@ parse_event_printing_config(const char *optarg, int enable)
> return 0;
> }
>
> +static int
> +parse_link_speed(int n)
> +{
> + uint32_t speed;
> +
> + switch (n) {
> + case 1000:
> + speed = ETH_LINK_SPEED_1G;
> + break;
> + case 10000:
> + speed = ETH_LINK_SPEED_10G;
> + break;
> + case 25000:
> + speed = ETH_LINK_SPEED_25G;
> + break;
> + case 40000:
> + speed = ETH_LINK_SPEED_40G;
> + break;
> + case 50000:
> + speed = ETH_LINK_SPEED_50G;
> + break;
> + case 100000:
> + speed = ETH_LINK_SPEED_100G;
> + break;
> + case 200000:
> + speed = ETH_LINK_SPEED_200G;
> + break;
Shouldn’t all of these fixed values be OR’d with ETH_LINK_SPEED_FIXED?
The testpmd command to change speed is also missing it.
-Andrew
...
prev parent reply other threads:[~2021-02-25 18:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 19:18 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
2021-03-05 19:42 ` [dpdk-dev] [PATCH v3] " Ajit Khaparde
2021-03-08 11:03 ` Ferruh Yigit
2021-02-25 18:33 ` Andrew Boyer [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=279CCAC7-AB50-4B2A-A724-C9DF1642A797@pensando.io \
--to=aboyer@pensando.io \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).