From: Ferruh Yigit <ferruh.yigit@intel.com>
To: John Daley <johndale@cisco.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] net/enic: fix packet loss after MTU change
Date: Mon, 23 Oct 2017 14:36:21 -0700 [thread overview]
Message-ID: <901823f6-5693-8f1c-0904-a007c8dbcaa2@intel.com> (raw)
In-Reply-To: <20171023202300.4944-1-johndale@cisco.com>
On 10/23/2017 1:23 PM, John Daley wrote:
> If multiple Rx queues and Rx Scatter are used and the MTU is
> modified so that the number of mbufs per packet changes, packet
> loss is possible.
>
> The enic completion queue index was miscalculated leaving the
> upper half of the queues uninitialized after an MTU change, possibly
> leading to completions on those queues not getting processed.
>
> Fixes: c3e09182bcd6 ("net/enic: support scatter Rx in MTU update")
> Cc: stable@dpdk.org
>
> Signed-off-by: John Daley <johndale@cisco.com>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2017-10-23 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 20:23 John Daley
2017-10-23 21:36 ` Ferruh Yigit [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-23 20:01 John Daley
2017-10-23 19:48 John Daley
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=901823f6-5693-8f1c-0904-a007c8dbcaa2@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=johndale@cisco.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).