From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Yongseok Koh <yskoh@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, nelio.laranjeiro@6wind.com, hhaim@cisco.com
Subject: Re: [PATCH v2 0/2] net/mlx5: fix erroneous index handling for Tx ring
Date: Wed, 10 May 2017 00:10:33 +0200 [thread overview]
Message-ID: <20170509221033.GQ16218@6wind.com> (raw)
In-Reply-To: <cover.1494362396.git.yskoh@mellanox.com>
On Tue, May 09, 2017 at 01:49:29PM -0700, Yongseok Koh wrote:
> This patchset is to fix a critical bug which can occur in case of resource
> deficiency on Tx path. Flowing multi-segment packets can accelerate the
> occurrence rate.
>
> v2:
> * Split the patch into two separate ones to make back-port easier.
> * Added "Fiexes:" tag and "CC: stable@dpdk.org" for the bug fix.
>
> Yongseok Koh (2):
> net/mlx5: fix erroneous index handling for Tx ring
> net/mlx5: change error-prone code on Tx path
>
> drivers/net/mlx5/mlx5_rxtx.c | 51 +++++++++++++++++++-------------------------
> 1 file changed, 22 insertions(+), 29 deletions(-)
For the series:
Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Thanks for extracting the fix into a separate patch.
Ferruh, Thomas, is there still time to include this for 17.05 given the
seriousness of this bug?
--
Adrien Mazarguil
6WIND
next prev parent reply other threads:[~2017-05-09 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-06 1:20 [PATCH] net/mlx5: fix erroneous index handling for Tx ring Yongseok Koh
2017-05-09 20:49 ` [PATCH v2 0/2] " Yongseok Koh
2017-05-09 20:49 ` [PATCH v2 1/2] " Yongseok Koh
2017-05-09 20:49 ` [PATCH v2 2/2] net/mlx5: change error-prone code on Tx path Yongseok Koh
2017-05-09 22:10 ` Adrien Mazarguil [this message]
2017-05-10 16:06 ` [PATCH v2 0/2] net/mlx5: fix erroneous index handling for Tx ring Thomas Monjalon
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=20170509221033.GQ16218@6wind.com \
--to=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hhaim@cisco.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=thomas@monjalon.net \
--cc=yskoh@mellanox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.