[dpdk-dev] [PATCH v3 0/2] testpmd: simulating noisy host environment
Iremonger, Bernard
bernard.iremonger at intel.com
Fri May 11 13:50:17 CEST 2018
Hi Jens,
<snip>
> Subject: [dpdk-dev] [PATCH v3 0/2] testpmd: simulating noisy host
> environment
>
> This series adds a new forwarding mode 'noisy'. It proposes 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:
>
> --noisy-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).
>
> --noisy-flush-timeout [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:
>
> --noisy-memory-footprint [size]
> Size of the VNF internal memory (MB), in which the random read/write will
> be done, allocated by rte_malloc (hugepages).
>
> --noisy-nb-rnd-write [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.
>
> --noisy-nb-rnd-read [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.
>
> --noisy-nb-rnd-read-write [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.
>
> Comments are appreciated.
>
> regards,
> Jens
>
<snip>
This patch set does not apply to the current master branch, could you rebase please to the latest master branch.
Regards,
Bernard.
More information about the dev
mailing list