patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Michael Baum <michaelba@nvidia.com>
Cc: stable@dpdk.org, Matan Azrad <matan@nvidia.com>,
	 Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [PATCH 19.11 0/3] net/mlx5: fix MPRQ stride
Date: Mon, 11 Apr 2022 07:38:32 +0200	[thread overview]
Message-ID: <CAATJJ0L5Y-9HsU2Xgsw4G6OekSCf76FSBrjL+d1kxmLTFWKkTg@mail.gmail.com> (raw)
In-Reply-To: <20220410085217.922084-1-michaelba@nvidia.com>

On Sun, Apr 10, 2022 at 10:52 AM Michael Baum <michaelba@nvidia.com> wrote:
>
> All these three patches resolve the same issue.

Thank you Michael,
enqueued for a 19.11.13 release later this year

> Michael Baum (3):
>   net/mlx5: add minimum WQE size for striding RQ
>   net/mlx5: improve stride parameter names
>   net/mlx5: fix MPRQ stride devargs adjustment
>
>  drivers/net/mlx5/mlx5.c           |  55 ++------
>  drivers/net/mlx5/mlx5.h           |  13 +-
>  drivers/net/mlx5/mlx5_defs.h      |   4 +-
>  drivers/net/mlx5/mlx5_devx_cmds.c |  28 ++++
>  drivers/net/mlx5/mlx5_prm.h       |  38 +++++-
>  drivers/net/mlx5/mlx5_rxq.c       | 220 ++++++++++++++++++++----------
>  drivers/net/mlx5/mlx5_rxtx.c      |  14 +-
>  drivers/net/mlx5/mlx5_rxtx.h      |   4 +-
>  8 files changed, 243 insertions(+), 133 deletions(-)
>
> --
> 2.25.1
>


-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

      parent reply	other threads:[~2022-04-11  5:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-10  8:52 Michael Baum
2022-04-10  8:52 ` [PATCH 19.11 1/3] net/mlx5: add minimum WQE size for striding RQ Michael Baum
2022-04-10  8:52 ` [PATCH 19.11 2/3] net/mlx5: improve stride parameter names Michael Baum
2022-04-10  8:52 ` [PATCH 19.11 3/3] net/mlx5: fix MPRQ stride devargs adjustment Michael Baum
2022-04-11  5: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=CAATJJ0L5Y-9HsU2Xgsw4G6OekSCf76FSBrjL+d1kxmLTFWKkTg@mail.gmail.com \
    --to=christian.ehrhardt@canonical.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).