patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>, dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v1 0/5] net/mlx4: restore inner VXLAN & UDP RSS support
Date: Tue, 21 Nov 2017 09:41:17 -0500	[thread overview]
Message-ID: <20171121144117.GB1753@hmswarspite.think-freely.org> (raw)
In-Reply-To: <1511272929-17955-1-git-send-email-adrien.mazarguil@6wind.com>

On Tue, Nov 21, 2017 at 03:27:22PM +0100, Adrien Mazarguil wrote:
> Following the refactoring of the entire mlx4 PMD for DPDK 17.11, UDP RSS
> support was left in a disabled state. Likewise, inner VXLAN RSS used to be
> performed automatically by default but it's not the case anymore.
> 
> This series brings back both features by relying on the latest API updates
> and bugfixes in RDMA core and Linux. 
> 
> All patches are CC'ed stable since they target both DPDK 18.02 and 17.11.1.
> 
> Adrien Mazarguil (5):
>   net/mlx4: fix unnecessary include
>   net/mlx4: fix documentation in private structure
>   net/mlx4: use function to get default RSS fields
>   net/mlx4: restore UDP RSS by probing capabilities
>   net/mlx4: restore inner VXLAN RSS support
> 
>  drivers/net/mlx4/mlx4.c      | 21 +++++++++++++++++++++
>  drivers/net/mlx4/mlx4.h      | 10 ++++++++--
>  drivers/net/mlx4/mlx4_flow.c | 35 +++++++++++++++++++++--------------
>  drivers/net/mlx4/mlx4_flow.h |  1 +
>  drivers/net/mlx4/mlx4_txq.c  |  1 -
>  5 files changed, 51 insertions(+), 17 deletions(-)
> 
> -- 
> 2.1.4
> 

Looks reasonable

Acked-by: Neil Horman <nhorman@tuxdriver.com>

  parent reply	other threads:[~2017-11-21 14:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21 14:27 [dpdk-stable] " Adrien Mazarguil
2017-11-21 14:27 ` [dpdk-stable] [PATCH v1 1/5] net/mlx4: fix unnecessary include Adrien Mazarguil
2017-11-21 14:27 ` [dpdk-stable] [PATCH v1 2/5] net/mlx4: fix documentation in private structure Adrien Mazarguil
2017-11-21 14:27 ` [dpdk-stable] [PATCH v1 3/5] net/mlx4: use function to get default RSS fields Adrien Mazarguil
2017-11-21 14:27 ` [dpdk-stable] [PATCH v1 4/5] net/mlx4: restore UDP RSS by probing capabilities Adrien Mazarguil
2017-11-21 14:27 ` [dpdk-stable] [PATCH v1 5/5] net/mlx4: restore inner VXLAN RSS support Adrien Mazarguil
2017-11-21 14:41 ` Neil Horman [this message]
2017-11-23 17:37 ` [dpdk-stable] [PATCH v2 0/5] net/mlx4: restore inner VXLAN & UDP " Adrien Mazarguil
2017-11-23 17:37   ` [dpdk-stable] [PATCH v2 1/5] net/mlx4: fix unnecessary include Adrien Mazarguil
2017-11-23 17:37   ` [dpdk-stable] [PATCH v2 2/5] net/mlx4: fix documentation in private structure Adrien Mazarguil
2017-11-23 17:38   ` [dpdk-stable] [PATCH v2 3/5] net/mlx4: use function to get default RSS fields Adrien Mazarguil
2017-11-23 17:38   ` [dpdk-stable] [PATCH v2 4/5] net/mlx4: restore UDP RSS by probing capabilities Adrien Mazarguil
2017-11-23 17:38   ` [dpdk-stable] [PATCH v2 5/5] net/mlx4: restore inner VXLAN RSS support Adrien Mazarguil
2017-12-04 12:07   ` [dpdk-stable] [PATCH v2 0/5] net/mlx4: restore inner VXLAN & UDP " Shahaf Shuler

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=20171121144117.GB1753@hmswarspite.think-freely.org \
    --to=nhorman@tuxdriver.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.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).