From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Tudor Cornea <tudor.cornea@gmail.com>
Cc: stable@dpdk.org
Subject: Re: [PATCH 19.11] net/ixgbe: fix port initialization if MTU config fails
Date: Wed, 1 Dec 2021 16:38:47 +0100 [thread overview]
Message-ID: <CAATJJ0LZCKN2L9oa+WHz4FgVvXVhYVd5qeFEueMqGK=VYLH1tQ@mail.gmail.com> (raw)
In-Reply-To: <1638355193-117871-1-git-send-email-tudor.cornea@gmail.com>
On Wed, Dec 1, 2021 at 12:10 PM Tudor Cornea <tudor.cornea@gmail.com> wrote:
>
> [ upstream commit 2108930be123ab83c837e7dd6eb3078ec3482ad4 ]
>
Thanks, applied
> On a VMware ESXi 6.0 setup with an Intel 82599 NIC the ports don't
> seem to initialize anymore, while running testpmd.
>
> Configuring Port 0 (socket 0)
> ixgbevf_dev_rx_init(): Set max packet length to 1518 failed.
> ixgbevf_dev_start(): Unable to initialize RX hardware (-22)
> Fail to start port 0: Invalid argument
> Configuring Port 1 (socket 0)
> ixgbevf_dev_rx_init(): Set max packet length to 1518 failed.
> ixgbevf_dev_start(): Unable to initialize RX hardware (-22)
> Fail to start port 1: Invalid argument
> Please stop the ports first
>
> If the call to ixgbevf_rlpml_set_vf fails and we return prematurely,
> we will not be able to initialize the ports correctly.
>
> Fixes: c77866a16904 ("net/ixgbe: detect failed VF MTU set")
>
> We can make this particular use case work correctly if we don't
> return an error, which seems to be consistent with the overall
> kernel ixgbevf implementation.
>
> [1]
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/
> drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c?h=v5.14#n2015
>
> Signed-off-by: Tudor Cornea <tudor.cornea@gmail.com>
> ---
> drivers/net/ixgbe/ixgbe_rxtx.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/net/ixgbe/ixgbe_rxtx.c b/drivers/net/ixgbe/ixgbe_rxtx.c
> index ed36a33..26b49a2 100644
> --- a/drivers/net/ixgbe/ixgbe_rxtx.c
> +++ b/drivers/net/ixgbe/ixgbe_rxtx.c
> @@ -5545,11 +5545,9 @@ ixgbevf_dev_rx_init(struct rte_eth_dev *dev)
> * VF packets received can work in all cases.
> */
> if (ixgbevf_rlpml_set_vf(hw,
> - (uint16_t)dev->data->dev_conf.rxmode.max_rx_pkt_len)) {
> + (uint16_t)dev->data->dev_conf.rxmode.max_rx_pkt_len))
> PMD_INIT_LOG(ERR, "Set max packet length to %d failed.",
> dev->data->dev_conf.rxmode.max_rx_pkt_len);
> - return -EINVAL;
> - }
>
> /*
> * Assume no header split and no VLAN strip support
> --
> 2.7.4
>
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
prev parent reply other threads:[~2021-12-01 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 10:39 Tudor Cornea
2021-12-01 15:38 ` Christian Ehrhardt [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='CAATJJ0LZCKN2L9oa+WHz4FgVvXVhYVd5qeFEueMqGK=VYLH1tQ@mail.gmail.com' \
--to=christian.ehrhardt@canonical.com \
--cc=stable@dpdk.org \
--cc=tudor.cornea@gmail.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).