From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rasesh Mody <rmody@marvell.com>,
Shahed Shaikh <shshaikh@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH 1/1] net/qede: fix receive packet drop
Date: Tue, 19 Mar 2019 19:01:18 +0000 [thread overview]
Message-ID: <191681db-035a-fb28-b957-9e4023349b3d@intel.com> (raw)
Message-ID: <20190319190118.pnAgZVxKey46cnJwH3e_9mQMzndOq1cKdCxoVup1Klk@z> (raw)
In-Reply-To: <BYAPR18MB28380870FE77D5EA03190661B54A0@BYAPR18MB2838.namprd18.prod.outlook.com>
On 3/13/2019 5:55 PM, Rasesh Mody wrote:
>> From: dev <dev-bounces@dpdk.org> On Behalf Of Shahed Shaikh
>> Sent: Tuesday, March 12, 2019 9:51 AM
>>
>> There is a corner case in which driver won't post receive buffers when driver
>> has processed all received packets in single loop (i.e. hw_consumer ==
>> sw_consumer) and then HW will start dropping packets since it did not see
>> new receive buffers posted.
>>
>> This corner case is seen when size of Rx ring is less than or equals Rx packet
>> burst count for dev->rx_pkt_burst().
>>
>> Fixes: 8f2312474529 ("net/qede: fix performance bottleneck in Rx path")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Shahed Shaikh <shshaikh@marvell.com>
>> ---
>
> Acked-by: Rasesh Mody <rmody@marvell.com>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2019-03-19 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 16:51 [dpdk-dev] " Shahed Shaikh
2019-03-13 17:55 ` Rasesh Mody
2019-03-19 19:01 ` Ferruh Yigit [this message]
2019-03-19 19:01 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
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=191681db-035a-fb28-b957-9e4023349b3d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=rmody@marvell.com \
--cc=shshaikh@marvell.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).