From: "Smoczynski, MarcinX" <marcinx.smoczynski@intel.com>
To: "Gavin Hu (Arm Technology China)" <Gavin.Hu@arm.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Wiles, Keith" <keith.wiles@intel.com>,
"adrien.mazarguil@6wind.com" <adrien.mazarguil@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
"Drost, MariuszX" <mariuszx.drost@intel.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v1] net/tap: fix blocked rx packets error
Date: Fri, 6 Sep 2019 08:48:04 +0000 [thread overview]
Message-ID: <2F25558C1648FA498380EAC12A86126215FFBB79@HASMSX110.ger.corp.intel.com> (raw)
In-Reply-To: <VI1PR08MB53764DD31C010BEBFCF454F78FBB0@VI1PR08MB5376.eurprd08.prod.outlook.com>
> -----Original Message-----
> From: Gavin Hu (Arm Technology China) [mailto:Gavin.Hu@arm.com]
> Sent: Thursday, September 5, 2019 7:44 AM
> To: Smoczynski, MarcinX <marcinx.smoczynski@intel.com>; Ananyev,
> Konstantin <konstantin.ananyev@intel.com>; Wiles, Keith
> <keith.wiles@intel.com>; adrien.mazarguil@6wind.com
> Cc: dev@dpdk.org; stable@dpdk.org; Drost, MariuszX
> <mariuszx.drost@intel.com>
> Subject: RE: [dpdk-dev] [PATCH v1] net/tap: fix blocked rx packets error
>
> HI Marcin,
>
> > -----Original Message-----
> > From: dev <dev-bounces@dpdk.org> On Behalf Of Marcin Smoczynski
> > Sent: Monday, September 2, 2019 7:43 PM
> > To: konstantin.ananyev@intel.com; keith.wiles@intel.com;
> > adrien.mazarguil@6wind.com
> > Cc: dev@dpdk.org; stable@dpdk.org; Marcin Smoczynski
> > <marcinx.smoczynski@intel.com>; Mariusz Drost
> > <mariuszx.drost@intel.com>
> > Subject: [dpdk-dev] [PATCH v1] net/tap: fix blocked rx packets error
> >
> > When OS sends more packets than are beaing read with a single
> s/ beaing/being
Thanks for that, will be corrected in the v2.
>
> > '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.
> >
> > Fixes: a0d8e807d9 ("net/tap: add Rx trigger")
> > Cc: stable@dpdk.org
> >
> > Tested-by: Mariusz Drost <mariuszx.drost@intel.com>
> > Signed-off-by: Marcin Smoczynski <marcinx.smoczynski@intel.com>
> > ---
> > drivers/net/tap/rte_eth_tap.c | 6 ++++--
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/net/tap/rte_eth_tap.c
> > b/drivers/net/tap/rte_eth_tap.c index 64bd04911..60121ae56 100644
> > --- a/drivers/net/tap/rte_eth_tap.c
> > +++ b/drivers/net/tap/rte_eth_tap.c
> > @@ -353,8 +353,7 @@ pmd_rx_burst(void *queue, struct rte_mbuf
> **bufs,
> > uint16_t nb_pkts)
> >
> > if (trigger == rxq->trigger_seen)
> > return 0;
> > - if (trigger)
> > - rxq->trigger_seen = trigger;
> > +
> > process_private = rte_eth_devices[rxq->in_port].process_private;
> > rte_compiler_barrier();
> I see this compiler barrier was added together with the above "rxq-
> >trigger_seen = trigger", should it be removed or moved together
> downwards?
I think it could be removed, but it is best to ask author of the original code.
Adrien, what do you think about removing this barrier?
>
> > for (num_rx = 0; num_rx < nb_pkts; ) { @@ -433,6 +432,9 @@
> > pmd_rx_burst(void *queue, struct rte_mbuf **bufs, uint16_t nb_pkts)
> > rxq->stats.ipackets += num_rx;
> > rxq->stats.ibytes += num_rx_bytes;
> >
> > + if (trigger && num_rx < nb_pkts)
> > + rxq->trigger_seen = trigger;
> > +
> > return num_rx;
> > }
> >
> > --
> > 2.17.1
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended recipient,
> please notify the sender immediately and do not disclose the contents to any
> other person, use it for any purpose, or store or copy the information in any
> medium. Thank you.
next prev parent reply other threads:[~2019-09-06 8:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 11:43 [dpdk-stable] " Marcin Smoczynski
2019-09-03 13:15 ` Ananyev, Konstantin
2019-09-05 5:43 ` [dpdk-stable] [dpdk-dev] " Gavin Hu (Arm Technology China)
2019-09-06 8:48 ` Smoczynski, MarcinX [this message]
2019-09-23 13:22 ` [dpdk-stable] [PATCH v2 0/1] " Marcin Smoczynski
2019-09-23 13:22 ` [dpdk-stable] [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=2F25558C1648FA498380EAC12A86126215FFBB79@HASMSX110.ger.corp.intel.com \
--to=marcinx.smoczynski@intel.com \
--cc=Gavin.Hu@arm.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--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).