From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: "wei.guo.simon@gmail.com" <wei.guo.simon@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4] app/testpmd: add option ring-bind-lcpu to bind Q with CPU
Date: Mon, 15 Jan 2018 08:31:52 +0000 [thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093B7109A8@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1515571177-24040-1-git-send-email-wei.guo.simon@gmail.com>
Hi Simon,
> -----Original Message-----
> From: wei.guo.simon@gmail.com [mailto:wei.guo.simon@gmail.com]
> Sent: Wednesday, January 10, 2018 4:00 PM
> To: Lu, Wenzhuo <wenzhuo.lu@intel.com>
> Cc: dev@dpdk.org; Simon Guo <wei.guo.simon@gmail.com>
> Subject: [PATCH v4] app/testpmd: add option ring-bind-lcpu to bind Q with
> CPU
>
> From: Simon Guo <wei.guo.simon@gmail.com>
>
> Currently the rx/tx queue is allocated from the buffer pool on socket of:
> - port's socket if --port-numa-config specified
> - or ring-numa-config setting per port
>
> All the above will "bind" queue to single socket per port configuration.
> But it can actually archieve better performance if one port's queue can be
> spread across multiple NUMA nodes, and the rx/tx queue is allocated per
> lcpu socket.
>
> This patch adds a new option "--ring-bind-lcpu"(no parameter). With this,
> testpmd can utilize the PCI-e bus bandwidth on another NUMA nodes.
>
> When --port-numa-config or --ring-numa-config option is specified, this --
> ring-bind-lcpu option will be suppressed.
>
> Test result:
> 64bytes package, running in PowerPC with Mellanox
> CX-4 card, single port(100G), with 8 cores, fw mode:
> - Without this patch: 52.5Mpps throughput
> - With this patch: 66Mpps throughput
> ~25% improvement
>
> Signed-off-by: Simon Guo <wei.guo.simon@gmail.com>
This patch is fine. But for the new parameter, please update this doc, run_app.rst. Thanks.
next prev parent reply other threads:[~2018-01-15 8:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 7:59 wei.guo.simon
2018-01-14 23:30 ` Thomas Monjalon
2018-01-16 2:12 ` Simon Guo
2018-01-15 8:31 ` Lu, Wenzhuo [this message]
2018-01-13 2:35 ` [dpdk-dev] [PATCH v5] " wei.guo.simon
2018-01-16 2:54 ` Lu, Wenzhuo
2018-01-16 12:38 ` Ananyev, Konstantin
2018-01-18 2:17 ` Simon Guo
2018-01-18 12:14 ` Ananyev, Konstantin
2018-01-25 3:40 ` Simon Guo
2019-04-05 15:09 ` Ferruh Yigit
2019-04-05 15:09 ` Ferruh Yigit
2018-01-16 2:13 ` [dpdk-dev] [PATCH v4] " Simon Guo
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=6A0DE07E22DDAD4C9103DF62FEBC09093B7109A8@shsmsx102.ccr.corp.intel.com \
--to=wenzhuo.lu@intel.com \
--cc=dev@dpdk.org \
--cc=wei.guo.simon@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).