DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: "Donald_Lee@trendmicro.com" <Donald_Lee@trendmicro.com>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/tap: fix Rx miss the packets
Date: Fri, 12 Jul 2019 13:50:13 +0000	[thread overview]
Message-ID: <E7C458C8-CC76-4F32-B427-D34851CD9D36@intel.com> (raw)
In-Reply-To: <F66F7AE0-3057-472E-988E-C6A48D9C7201@trendmicro.com>



> On Jul 12, 2019, at 5:20 AM, Donald_Lee@trendmicro.com wrote:
> 
> From: Donald Lee <donald_lee@trendmicro.com>
> 
> 
> 
> After pmd_rx_burst be triggered, it doesn't retrieve all the frames.
> 
> It may leave some pending frames there.
> 
> 
> 
> Signed-off-by: Donald Lee <donald_lee@trendmicro.com>
> 
> ---
> 
> drivers/net/tap/rte_eth_tap.c | 7 ++++++-
> 
> drivers/net/tap/rte_eth_tap.h | 1 +
> 
> 2 files changed, 7 insertions(+), 1 deletion(-)
> 

Acked-by: Keith Wiles <keith.wiles@intel.com>

Regards,
Keith


  reply	other threads:[~2019-07-12 13:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12 10:20 Donald_Lee
2019-07-12 13:50 ` Wiles, Keith [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-07-04 16:11 Donald_Lee
2019-07-04 16:42 ` Thomas Monjalon

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=E7C458C8-CC76-4F32-B427-D34851CD9D36@intel.com \
    --to=keith.wiles@intel.com \
    --cc=Donald_Lee@trendmicro.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).