patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Erez Ferber <erezf@mellanox.com>, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] net/mlx5: fix MTU update
Date: Wed, 07 Feb 2018 15:24:01 +0000	[thread overview]
Message-ID: <1518017041.15424.17.camel@debian.org> (raw)
In-Reply-To: <1518015868-21957-1-git-send-email-erezf@mellanox.com>

On Wed, 2018-02-07 at 17:04 +0200, Erez Ferber wrote:
> Changing the MTU is not related to changing the number of segments,
> activating or not the multi-segment support should be handled by the
> application.
> 
> Signed-off-by: Erez Ferber <erezf@mellanox.com>
> ---
> 
> This backport is intended for 16-11 and is based on commit
> a0edafe4099b1ef139242abb7baa2c2a48b83fd2
> 
> ---
>  
> drivers/net/mlx5/mlx5_ethdev.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/drivers/net/mlx5/mlx5_ethdev.c
> b/drivers/net/mlx5/mlx5_ethdev.c
> index c0f73e9..f73d26e 100644
> --- a/drivers/net/mlx5/mlx5_ethdev.c
> +++ b/drivers/net/mlx5/mlx5_ethdev.c
> @@ -930,9 +930,7 @@ recover:
>  		/* Provide new values to rxq_setup(). */
>  		dev->data->dev_conf.rxmode.jumbo_frame = sp;
>  		dev->data->dev_conf.rxmode.max_rx_pkt_len =
> max_frame_len;
> -		if (rehash)
> -			ret = rxq_rehash(dev, rxq_ctrl);
> -		else
> +		if (!rehash)
>  			ret = rxq_ctrl_setup(dev, rxq_ctrl, 1 <<
> rxq->elts_n,
>  					     rxq_ctrl->socket, NULL,
> rxq->mp);
>  		if (!ret)

Thanks, applied, will be pushed with the updates from -rc2 and -rc3
shortly.

-- 
Kind regards,
Luca Boccassi

  reply	other threads:[~2018-02-07 15:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07 15:04 Erez Ferber
2018-02-07 15:24 ` Luca Boccassi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-08-01  7:55 Nelio Laranjeiro
2017-08-02 23:13 ` Yongseok Koh

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=1518017041.15424.17.camel@debian.org \
    --to=bluca@debian.org \
    --cc=erezf@mellanox.com \
    --cc=stable@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).