From: Thomas Monjalon <thomas@monjalon.net>
To: Yongseok Koh <yskoh@mellanox.com>
Cc: dev@dpdk.org, Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
nelio.laranjeiro@6wind.com, hhaim@cisco.com
Subject: Re: [dpdk-dev] [PATCH v2 0/2] net/mlx5: fix erroneous index handling for Tx ring
Date: Wed, 10 May 2017 18:06:08 +0200 [thread overview]
Message-ID: <2632169.mBh21d6xNu@xps> (raw)
In-Reply-To: <20170509221033.GQ16218@6wind.com>
10/05/2017 00:10, Adrien Mazarguil:
> 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?
Applied, thanks
prev parent reply other threads:[~2017-05-10 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-06 1:20 [dpdk-dev] [PATCH] " Yongseok Koh
2017-05-09 20:49 ` [dpdk-dev] [PATCH v2 0/2] " Yongseok Koh
2017-05-09 20:49 ` [dpdk-dev] [PATCH v2 1/2] " Yongseok Koh
2017-05-09 20:49 ` [dpdk-dev] [PATCH v2 2/2] net/mlx5: change error-prone code on Tx path Yongseok Koh
2017-05-09 22:10 ` [dpdk-dev] [PATCH v2 0/2] net/mlx5: fix erroneous index handling for Tx ring Adrien Mazarguil
2017-05-10 16:06 ` Thomas Monjalon [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=2632169.mBh21d6xNu@xps \
--to=thomas@monjalon.net \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hhaim@cisco.com \
--cc=nelio.laranjeiro@6wind.com \
--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 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).