DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "Jack Bond-Preston" <jack.bond-preston@foss.arm.com>,
	"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
	"Morten Brørup" <mb@smartsharesystems.com>,
	dev@dpdk.org, "Wathsala Vithanage" <wathsala.vithanage@arm.com>
Subject: Re: [PATCH] doc: clarify mempool striding optimisation on Arm
Date: Wed, 17 Jul 2024 11:40:04 +0100	[thread overview]
Message-ID: <ZpefhDd0Kyq16agr@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20240716192541.282e4cd6@hermes.local>

On Tue, Jul 16, 2024 at 07:25:41PM -0700, Stephen Hemminger wrote:
> On Mon, 15 Jul 2024 15:44:20 +0100
> Jack Bond-Preston <jack.bond-preston@foss.arm.com> wrote:
> 
> > The mempool memory channel striding optimisation is not necessary on
> > Arm platforms.
> > Update the Programmer's Guide's mempool section to clarify this.
> > 
> > Signed-off-by: Jack Bond-Preston <jack.bond-preston@foss.arm.com>
> > Reviewed-by: Wathsala Vithanage <wathsala.vithanage@arm.com>
> > ---
> 
> The whole memory channels argument has been a problem from day 0 of DPDK.
> There is no good way to find it from the OS, and it was never clear how much impact
> it had anyway. It would simplify users experience if it was deprecated or at least
> not required and rarely used.

The default for mempools (at least on x86) is set to 4 which is a
reasonable value, and so specifying memory channels is not really required
for running DPDK in most cases (I never use the -n flag when running tests
myself). While I don't think we should deprecate the option, I feel it
should be removed from our examples and scripts.  Hopefully in future a
method of determining memory channels from code can be come up with that we
can use, but in the meantime using a sane default I feel is good enough.

/Bruce

  reply	other threads:[~2024-07-17 10:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15 14:44 Jack Bond-Preston
2024-07-17  2:25 ` Stephen Hemminger
2024-07-17 10:40   ` Bruce Richardson [this message]
2024-07-29 19:46 ` Thomas Monjalon

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=ZpefhDd0Kyq16agr@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=jack.bond-preston@foss.arm.com \
    --cc=mb@smartsharesystems.com \
    --cc=stephen@networkplumber.org \
    --cc=wathsala.vithanage@arm.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).