DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Cian Ferriter <cian.ferriter@intel.com>,
	John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>
Cc: dev@dpdk.org, jonathan.ribas@fraudbuster.mobi
Subject: Re: [dpdk-dev] [PATCH 19.08 v2] doc: announce infinite Rx PCAP PMD feature
Date: Wed, 3 Jul 2019 15:06:18 +0100	[thread overview]
Message-ID: <9625d5da-aa84-9f30-74e0-92c9c83b1e24@intel.com> (raw)
In-Reply-To: <20190703110416.13193-1-cian.ferriter@intel.com>

On 7/3/2019 12:04 PM, Cian Ferriter wrote:
> This feature was added in the following commit:
> commit a3f5252e5cbd ("net/pcap: enable infinitely Rx a pcap file")
> 
> Signed-off-by: Cian Ferriter <cian.ferriter@intel.com>

<...>

> @@ -116,6 +116,12 @@ New Features
>    * Enabled need_wakeup feature which can provide efficient support for case
>      that application and driver executing on the same core.
>  
> +* **Enabled infinite Rx in the PCAP PMD.**
> +
> +  Added an infinite Rx feature which allows packets in the Rx PCAP of a PCAP
> +  device to be received repeatedly at a high rate. This can be useful for quick
> +  performance testing of DPDK apps.
> +

Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied to dpdk-next-net/master, thanks.


(cc'ed Jonathan, this feature looks like his "dpdk-burst-replay" [1], in case he
is interested.)


[1]: http://git.dpdk.org/apps/dpdk-burst-replay/

      parent reply	other threads:[~2019-07-03 14:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-03 11:04 Cian Ferriter
2019-07-03 11:21 ` Ferriter, Cian
2019-07-03 14:06 ` Ferruh Yigit [this message]

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=9625d5da-aa84-9f30-74e0-92c9c83b1e24@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=cian.ferriter@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=jonathan.ribas@fraudbuster.mobi \
    --cc=marko.kovacevic@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).