DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	Jens Freimann <jfreimann@redhat.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "ailan@redhat.com" <ailan@redhat.com>,
	"jan.scheurich@ericsson.com" <jan.scheurich@ericsson.com>,
	"vkaplans@redhat.com" <vkaplans@redhat.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] testpmd: add parameters buffersize-before-send and flush-timeout
Date: Thu, 12 Apr 2018 17:30:54 +0100	[thread overview]
Message-ID: <22853253-69d9-b064-ef29-66ca19fb7846@intel.com> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB977258AE914601@IRSMSX102.ger.corp.intel.com>

On 4/12/2018 3:57 PM, Ananyev, Konstantin wrote:
> Hi,
> 
>>
>> Create a fifo to buffer received packets. Once it flows over put
>> those packets into the actual tx queue. The fifo is created per tx
>> queue and its size can be set with the --buffersize-before-sending
>> commandline parameter.
>>
>> A second commandline parameter is used to set a timeout in
>> milliseconds after which the fifo is flushed.
>>
>> --buffersize-before-sending [packet numbers]
>> Keep the mbuf in a FIFO and forward the over flooding packets from the
>> FIFO. This queue is per TX-queue (after all other packet processing).
>>
>> --flush-timer [delay]
>> Flush the packet queue if no packets have been seen during
>> [delay]. As long as packets are seen, the timer is reset.
>>
> 
> I understand your desire to have some realistic fwd scenario,
> but why it all have to be put in iowfd mode?
>  iowfd is the simplest one, mainly used to test raw PMD pefomance
> in nearly ideal conditions.
> Why not to create your own forwarding mode (as most people do)?
> That way you'll have your 'real world app' test scenario,
> while keeping iofwd code small and simple.

+1 to having own forwarding mode for noisy neighbor, and leaving iofwd simple.

> Konstantin 
> 
>> Signed-off-by: Jens Freimann <jfreimann@redhat.com>

<...>

  reply	other threads:[~2018-04-12 16:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12 14:34 [dpdk-dev] [PATCH 0/2] testpmd: simulating noisy host environment Jens Freimann
2018-04-12 14:34 ` [dpdk-dev] [PATCH 1/2] testpmd: add parameters buffersize-before-send and flush-timeout Jens Freimann
2018-04-12 14:57   ` Ananyev, Konstantin
2018-04-12 16:30     ` Ferruh Yigit [this message]
2018-04-13  6:54       ` Jens Freimann
2018-04-12 14:34 ` [dpdk-dev] [PATCH 2/2] testpmd: add code to simulate noisy neighbour memory usage Jens Freimann

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=22853253-69d9-b064-ef29-66ca19fb7846@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=ailan@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=jan.scheurich@ericsson.com \
    --cc=jfreimann@redhat.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=thomas@monjalon.net \
    --cc=vkaplans@redhat.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).