From: Marcin Smoczynski <marcinx.smoczynski@intel.com>
To: konstantin.ananyev@intel.com, keith.wiles@intel.com,
adrien.mazarguil@6wind.com, ferruh.yigit@intel.com
Cc: dev@dpdk.org, mariuszx.drost@intel.com, stable@dpdk.org,
Marcin Smoczynski <marcinx.smoczynski@intel.com>
Subject: [dpdk-dev] [PATCH v2 0/1] net/tap: fix blocked rx packets error
Date: Mon, 23 Sep 2019 15:22:46 +0200 [thread overview]
Message-ID: <20190923132247.16860-1-marcinx.smoczynski@intel.com> (raw)
In-Reply-To: <20190902114310.15928-1-marcinx.smoczynski@intel.com>
When OS sends more packets than are being read with a single
'rte_eth_rx_burst' call, rx packets are getting stucked in the tap pmd
and are unable to receive, because trigger_seen is getting updated
and consecutive calls are not getting any packets.
Do not update trigger_seen unless less than a max number of packets were
received allowing next call to receive the rest.
v1 to v2 changes:
- fix typo in commit description
- remove unnecessary compiler barrier
Marcin Smoczynski (1):
net/tap: fix blocked rx packets error
drivers/net/tap/rte_eth_tap.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
--
2.17.1
next prev parent reply other threads:[~2019-09-23 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 11:43 [dpdk-dev] [PATCH v1] " Marcin Smoczynski
2019-09-03 13:15 ` Ananyev, Konstantin
2019-09-05 5:43 ` Gavin Hu (Arm Technology China)
2019-09-06 8:48 ` Smoczynski, MarcinX
2019-09-23 13:22 ` Marcin Smoczynski [this message]
2019-09-23 13:22 ` [dpdk-dev] [PATCH v2 1/1] " Marcin Smoczynski
2019-09-23 14:41 ` Wiles, Keith
2019-10-10 14:40 ` 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=20190923132247.16860-1-marcinx.smoczynski@intel.com \
--to=marcinx.smoczynski@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=keith.wiles@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=mariuszx.drost@intel.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).