From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: Xiaoyun Li <xiaoyun.li@intel.com>, Rosen Xu <rosen.xu@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Ivan Ilchenko <ivan.ilchenko@oktetlabs.ru>,
dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: fix MTU configuration before device start
Date: Mon, 25 Oct 2021 11:06:31 -0700 [thread overview]
Message-ID: <CACZ4nhu=qdLeGmhs3NNbLucoYfDLPaZ+9GaiMYgvuBZSPQp_jQ@mail.gmail.com> (raw)
In-Reply-To: <20211024164237.2116166-1-andrew.rybchenko@oktetlabs.ru>
On Sun, Oct 24, 2021 at 9:42 AM Andrew Rybchenko
<andrew.rybchenko@oktetlabs.ru> wrote:
>
> There is no point to do rte_eth_dev_mtu_set() before configure since
> set MTU value is overwritten on configure anyway. So, setting of MTU
> before configure is rejected now on ethdev level.
>
> If testpmd is going to do configure (e.g. just after testpmd start
> with disabled devices start up or any configuration changes in stopped
> state which require reconfigure), just save requested MTU in device
> config to be applied on reconfigure.
>
> Fixes: 1bb4a528c41f ("ethdev: fix max Rx packet length")
> Fixes: be0433cf953c ("ethdev: forbid MTU set before device configure")
>
> Signed-off-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> ---
> app/test-pmd/config.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/app/test-pmd/config.c b/app/test-pmd/config.c
> index a18871d461..3b97164302 100644
> --- a/app/test-pmd/config.c
> +++ b/app/test-pmd/config.c
> @@ -1241,10 +1241,12 @@ port_mtu_set(portid_t port_id, uint16_t mtu)
> if (port_id_is_invalid(port_id, ENABLED_WARN))
> return;
>
> - diag = rte_eth_dev_set_mtu(port_id, mtu);
> - if (diag != 0) {
> - fprintf(stderr, "Set MTU failed. diag=%d\n", diag);
> - return;
> + if (port->need_reconfig == 0) {
> + diag = rte_eth_dev_set_mtu(port_id, mtu);
> + if (diag != 0) {
> + fprintf(stderr, "Set MTU failed. diag=%d\n", diag);
> + return;
> + }
> }
>
> port->dev_conf.rxmode.mtu = mtu;
> --
> 2.30.2
>
next prev parent reply other threads:[~2021-10-25 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 16:42 Andrew Rybchenko
2021-10-25 18:06 ` Ajit Khaparde [this message]
2021-10-28 18:23 ` Ferruh Yigit
2021-11-02 2:37 ` Jiang, YuX
2021-11-10 7:23 ` Jiang, YuX
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='CACZ4nhu=qdLeGmhs3NNbLucoYfDLPaZ+9GaiMYgvuBZSPQp_jQ@mail.gmail.com' \
--to=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ivan.ilchenko@oktetlabs.ru \
--cc=konstantin.ananyev@intel.com \
--cc=rosen.xu@intel.com \
--cc=xiaoyun.li@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).