DPDK patches and discussions
 help / color / mirror / Atom feed
From: Victor Kaplansky <vkaplans@redhat.com>
To: dev@dpdk.org
Cc: "Jingjing Wu\"\"Franck Baudin" <jingjing.wu@intel.com>,
	"Amnon Ilan" <ailan@redhat.com>,
	"Tim Irnich" <tim.irnich@ericsson.com>,
	"Georg Kunz" <georg.kunz@ericsson.com>,
	"Gabor Halász" <gabor.halasz@ericsson.com>,
	"Mechthild Buescher" <mechthild.buescher@ericsson.com>
Subject: [dpdk-dev] [RFC PATCH 0/4] testpmd: simulating noisy host environment
Date: Mon, 30 Oct 2017 02:41:05 -0400 (EDT)	[thread overview]
Message-ID: <656367172.34323219.1509345665467.JavaMail.zimbra@redhat.com> (raw)


This RFC patch propose enhancements to testpmd to simulate
more realistic behavior of a guest machine engaged in receiving
and sending packets performing Virtual Network Function (VNF).

The goal is to enable simple of measuring performance impact on cache and
memory footprint utilization from various VNF co-located on the
same host machine.

This series of patches adds the new command line switches to
testpmd:

--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. 


Options to simulate route lookups:

--memory-footprint [size]
    Size of the VNF internal memory (MB), in which the random
    read/write will be done, allocated by rte_malloc (hugepages).

--random-w-memory-access-per-packet [num]
    Number of random writes in memory per packet should be
    performed, simulating hit-flags update. 64 bits per write,
    all write in different cache lines.

--random-r-memory-access-per-packet [num]
    Number of random reads in memory per packet should be
    performed, simulating FIB/table lookups.  64 bits per read,
    all write in different cache lines.

--random-rw-memory-access-per-packet [num]
    Number of random reads and writes in memory per packet should
    be performed, simulating stats update. 64 bits per read-write, all
    reads and writes in different cache lines.


Options to simulate packet processing (encap/decap)

--read-packet-buf [0-100]
    Determine the percentage of cache lines of a packet mbuf that
    testpmd should read for every packet.

--write-packet-buf [0-100]
    Determines the percentage of cache lines in the packet mbuf
    testpmd should write to.



Comments are welcomed. If name of command line switches seems
reasonable, I'll send rest of the patches with the implementation
in few days.

Regards,
-- 
Victor

             reply	other threads:[~2017-10-30  6:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30  6:41 Victor Kaplansky [this message]
2017-10-31 10:13 ` Bruce Richardson
2017-11-09 21:13   ` Thomas Monjalon
2017-11-13  9:41     ` Victor Kaplansky

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=656367172.34323219.1509345665467.JavaMail.zimbra@redhat.com \
    --to=vkaplans@redhat.com \
    --cc=ailan@redhat.com \
    --cc=dev@dpdk.org \
    --cc=gabor.halasz@ericsson.com \
    --cc=georg.kunz@ericsson.com \
    --cc=jingjing.wu@intel.com \
    --cc=mechthild.buescher@ericsson.com \
    --cc=tim.irnich@ericsson.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).