From: Jack Bond-Preston <jack.bond-preston@foss.arm.com>
To: "Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
"Morten Brørup" <mb@smartsharesystems.com>
Cc: dev@dpdk.org, Wathsala Vithanage <wathsala.vithanage@arm.com>
Subject: [PATCH] doc: clarify mempool striding optimisation on Arm
Date: Mon, 15 Jul 2024 15:44:20 +0100 [thread overview]
Message-ID: <20240715144420.36292-1-jack.bond-preston@foss.arm.com> (raw)
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>
---
doc/guides/prog_guide/mempool_lib.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/guides/prog_guide/mempool_lib.rst b/doc/guides/prog_guide/mempool_lib.rst
index 4db577fe18..988b0e80c1 100644
--- a/doc/guides/prog_guide/mempool_lib.rst
+++ b/doc/guides/prog_guide/mempool_lib.rst
@@ -77,6 +77,12 @@ When creating a new pool, the user can specify to use this feature or not.
.. _mempool_local_cache:
+.. note::
+
+ This feature is not present for Arm systems. Modern Arm Interconnects choose the SN-F (memory
+ channel) using a hash of memory address bits. As a result, the load is distributed evenly in all
+ cases, including the above described, rendering this feature unnecessary.
+
Local Cache
-----------
--
2.34.1
next reply other threads:[~2024-07-15 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 14:44 Jack Bond-Preston [this message]
2024-07-17 2:25 ` Stephen Hemminger
2024-07-17 10:40 ` Bruce Richardson
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=20240715144420.36292-1-jack.bond-preston@foss.arm.com \
--to=jack.bond-preston@foss.arm.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--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).