patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: Michael Baum <michaelba@nvidia.com>, "stable@dpdk.org" <stable@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>, Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: RE: [PATCH 20.11] net/mlx5: fix LRO validation in Rx setup
Date: Tue, 28 Jun 2022 13:39:40 +0000	[thread overview]
Message-ID: <DM4PR12MB537331660805F769AC86896DA1B89@DM4PR12MB5373.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220626104344.3047555-1-michaelba@nvidia.com>

Hi Michael,

The patch can't compile with the 20.11 LTS work queue. Please rebase with the below branch:

    https://github.com/steevenlee/dpdk 

Thanks,
Xueming

> -----Original Message-----
> From: Michael Baum <michaelba@nvidia.com>
> Sent: Sunday, June 26, 2022 6:44 PM
> To: stable@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>; Xueming(Steven) Li <xuemingl@nvidia.com>
> Subject: [PATCH 20.11] net/mlx5: fix LRO validation in Rx setup
> 
> [ upstream commit a213b8682117711c8e92475c5bbb321a3d8428dd ]
> 
> The mlx5_rx_queue_setup() get LRO offload from user.
> 
> When LRO is configured, the LRO flag in rxq_data is set to 1.
> 
> This patch adds validation to make sure the LRO is supported.
> 
> Fixes: 17ed314 ("net/mlx5: allow LRO per Rx queue")
> 
> Signed-off-by: Michael Baum <michaelba@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> ---
>  drivers/net/mlx5/mlx5_rxq.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/drivers/net/mlx5/mlx5_rxq.c b/drivers/net/mlx5/mlx5_rxq.c index 4a263a5803..6fad968eee 100644
> --- a/drivers/net/mlx5/mlx5_rxq.c
> +++ b/drivers/net/mlx5/mlx5_rxq.c
> @@ -756,6 +756,14 @@ mlx5_rx_queue_setup(struct rte_eth_dev *dev, uint16_t idx, uint16_t desc,
>  	uint16_t n_seg = conf->rx_nseg;
>  	int res;
> 
> +	if ((offloads & RTE_ETH_RX_OFFLOAD_TCP_LRO) &&
> +	    !priv->config.lro.supported) {
> +		DRV_LOG(ERR,
> +			"Port %u queue %u LRO is configured but not supported.",
> +			dev->data->port_id, idx);
> +		rte_errno = EINVAL;
> +		return -rte_errno;
> +	}
>  	if (mp) {
>  		/*
>  		 * The parameters should be checked on rte_eth_dev layer.
> --
> 2.25.1


  reply	other threads:[~2022-06-28 13:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-26 10:43 Michael Baum
2022-06-28 13:39 ` Xueming(Steven) Li [this message]
2022-06-28 15:33 ` [PATCH 20.11 v2] " Michael Baum
2022-06-29  7:24   ` Xueming(Steven) Li

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=DM4PR12MB537331660805F769AC86896DA1B89@DM4PR12MB5373.namprd12.prod.outlook.com \
    --to=xuemingl@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=michaelba@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=viacheslavo@nvidia.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).