From: Thomas Monjalon <thomas@monjalon.net>
To: Chengwen Feng <fengchengwen@huawei.com>
Cc: dev@dpdk.org, kevin.laatz@intel.com,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v2] examples/dma: support DMA dequeue when no packet received
Date: Mon, 03 Oct 2022 18:21:50 +0200 [thread overview]
Message-ID: <7433532.nlapOpYt14@thomas> (raw)
In-Reply-To: <Yt6RApVZEbEiXOtB@bricha3-MOBL.ger.corp.intel.com>
25/07/2022 14:48, Bruce Richardson:
> On Mon, Jul 25, 2022 at 08:22:00PM +0800, Chengwen Feng wrote:
> > Currently the example using DMA in asynchronous mode, which are:
> > nb_rx = rte_eth_rx_burst();
> > if (nb_rx == 0)
> > continue;
> > ...
> > dma_enqueue(); // enqueue the received packets copy request
> > nb_cpl = dma_dequeue(); // get copy completed packets
> > ...
> >
> > There are no waiting inside dma_dequeue(), and this is why it's called
> > asynchronus. If there are no packet received, it won't call
> > dma_dequeue(), but some packets may still in the DMA queue which
> > enqueued in last cycle. As a result, when the traffic is stopped, the
> > sent packets and received packets are unbalanced from the perspective
> > of the traffic generator.
> >
> > The patch supports DMA dequeue when no packet received, it helps to
> > judge the test result by comparing the sent packets with the received
> > packets on traffic generator sides.
> >
> > Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Kevin Laatz <kevin.laatz@intel.com>
Applied, thanks.
next prev parent reply other threads:[~2022-10-03 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 12:22 Chengwen Feng
2022-07-25 12:48 ` Bruce Richardson
2022-10-03 16:21 ` Thomas Monjalon [this message]
2022-07-26 8:49 ` Kevin Laatz
2022-09-13 1:44 ` fengchengwen
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=7433532.nlapOpYt14@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=kevin.laatz@intel.com \
/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).