DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Shahaf Shuler <shahafs@mellanox.com>,
	Yongseok Koh <yskoh@mellanox.com>,
	"Xueming(Steven) Li" <xuemingl@mellanox.com>
Cc: dpdk stable <stable@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] net/mlx5: fix interrupt completion queue index wrapping
Date: Mon, 10 Sep 2018 11:59:12 +0100	[thread overview]
Message-ID: <f61230d6-78ac-a907-a543-2fa03fe84ebd@intel.com> (raw)
In-Reply-To: <DB7PR05MB4426C6BFB3378664A57DC384C3030@DB7PR05MB4426.eurprd05.prod.outlook.com>

On 9/4/2018 7:21 AM, Shahaf Shuler wrote:
> Tuesday, August 28, 2018 9:59 PM, Yongseok Koh:
>> wrapping
>>
>>> On Aug 23, 2018, at 4:10 PM, Xueming Li <xuemingl@mellanox.com> wrote:
>>>
>>> Rxq cq_ci was 16 bits while hardware is expecting to wrap around 24
>>> bits, this caused interrupt failure after burst of packets.
>>>
>>> Fixes: 43e9d9794cde ("net/mlx5: support upstream rdma-core")
>>> Cc: Shahaf Shuler <shahafs@mellanox.com>

I assume you would want to backport the fix to stable releases, so adding:
Cc: stable@dpdk.org

Please shout if that is not the intention.

>>>
>>> Signed-off-by: Xueming Li <xuemingl@mellanox.com>
>>> ---
>> Acked-by: Yongseok Koh <yskoh@mellanox.com>
> 
> Applied to next-net-mlx, thanks. 
> 
>>
>> Thanks

      reply	other threads:[~2018-09-10 11:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-23 23:10 [dpdk-dev] " Xueming Li
2018-08-28 18:59 ` Yongseok Koh
2018-09-04  6:21   ` Shahaf Shuler
2018-09-10 10:59     ` Ferruh Yigit [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=f61230d6-78ac-a907-a543-2fa03fe84ebd@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=shahafs@mellanox.com \
    --cc=stable@dpdk.org \
    --cc=xuemingl@mellanox.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).