From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Mallesh Koujalagi <malleshx.koujalagi@intel.com>,
dev@dpdk.org, konstantin.ananyev@intel.com
Cc: mtetsuyah@gmail.com
Subject: Re: [dpdk-dev] [PATCH v2] net/null: support bulk allocation
Date: Fri, 16 Mar 2018 14:08:10 +0000 [thread overview]
Message-ID: <17d3b393-4f39-ca32-abf7-37b0e0dbdbed@intel.com> (raw)
In-Reply-To: <1f784f92-70fe-915c-8ca2-54539a7ceb60@intel.com>
On 3/9/2018 11:09 AM, Ferruh Yigit wrote:
> On 3/8/2018 11:40 PM, Mallesh Koujalagi wrote:
>> Bulk allocation of multiple mbufs increased more than ~2% and less
>> than 8% throughput on single core (1.8 GHz), based on usage for example
>> 1: Testpmd case: Two null devices with copy 8% improvement.
>> testpmd -c 0x3 -n 4 --socket-mem 1024,1024
>> --vdev 'eth_null0,size=64,copy=1' --vdev 'eth_null1,size=64,copy=1'
>> -- -i -a --coremask=0x2 --txrst=64 --txfreet=64 --txd=256
>> --rxd=256 --rxfreet=64 --burst=64 --txpt=64 --txq=1 --rxq=1 --numa
>> 2. Ovs switch case: 2% improvement.
>> $VSCTL add-port ovs-br dpdk1 -- set Interface dpdk1 type=dpdk \
>> options:dpdk-devargs=eth_null0,size=64,copy=1
>> $VSCTL add-port ovs-br dpdk2 -- set Interface dpdk2 type=dpdk \
>> options:dpdk-devargs=eth_null1,size=64,copy=1
>>
>> Signed-off-by: Mallesh Koujalagi <malleshx.koujalagi@intel.com>
>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-03-16 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-03 3:11 [dpdk-dev] [PATCH] net/null: Support bulk alloc and free Mallesh Koujalagi
2018-03-05 15:24 ` Ferruh Yigit
2018-03-05 15:36 ` Ananyev, Konstantin
2018-03-07 10:57 ` Ferruh Yigit
2018-03-08 21:29 ` Koujalagi, MalleshX
2018-03-08 23:40 ` [dpdk-dev] [PATCH v2] net/null: support bulk allocation Mallesh Koujalagi
2018-03-09 11:09 ` Ferruh Yigit
2018-03-16 14:08 ` 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=17d3b393-4f39-ca32-abf7-37b0e0dbdbed@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=malleshx.koujalagi@intel.com \
--cc=mtetsuyah@gmail.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).