From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: "phil.yang@arm.com" <phil.yang@arm.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "gavin.hu@arm.com" <gavin.hu@arm.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd: optimize membuf pool allocation
Date: Wed, 12 Sep 2018 10:15:42 +0000 [thread overview]
Message-ID: <8CEF83825BEC744B83065625E567D7C260CEF262@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <1536717266-6363-1-git-send-email-phil.yang@arm.com>
> -----Original Message-----
> From: phil.yang@arm.com [mailto:phil.yang@arm.com]
> Sent: Wednesday, September 12, 2018 2:54 AM
> To: dev@dpdk.org
> Cc: Iremonger, Bernard <bernard.iremonger@intel.com>; gavin.hu@arm.com;
> stable@dpdk.org; phil.yang@arm.com
> Subject: [PATCH v2] app/testpmd: optimize membuf pool allocation
>
> By default, testpmd will create membuf pool for all NUMA nodes and ignore EAL
> configuration.
>
> Count the number of available NUMA according to EAL core mask or core list
> configuration. Optimized by only creating membuf pool for those nodes.
>
> Fixes: c9cafcc ("app/testpmd: fix mempool creation by socket id")
>
> Signed-off-by: Phil Yang <phil.yang@arm.com>
> Acked-by: Gavin Hu <gavin.hu@arm.com>
Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
next prev parent reply other threads:[~2018-09-12 10:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 9:33 [dpdk-dev] [PATCH] app/testpmd: Optimize " Phil Yang
2018-08-27 9:39 ` Gavin Hu
2018-09-11 16:23 ` Iremonger, Bernard
2018-09-12 1:59 ` Phil Yang (Arm Technology China)
2018-09-12 1:54 ` [dpdk-dev] [PATCH v2] app/testpmd: optimize " Phil Yang
2018-09-12 10:15 ` Iremonger, Bernard [this message]
2018-09-19 13:38 ` Thomas Monjalon
2018-10-08 11:33 ` Ferruh Yigit
2018-10-08 11:35 ` Burakov, Anatoly
2018-10-11 7:11 ` Phil Yang (Arm Technology China)
2018-10-11 10:37 ` Phil Yang (Arm Technology China)
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=8CEF83825BEC744B83065625E567D7C260CEF262@IRSMSX107.ger.corp.intel.com \
--to=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=phil.yang@arm.com \
--cc=stable@dpdk.org \
/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).