DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vipin Varghese <vipin.varghese@amd.com>
To: <thomas@monjalon.net>, <dev@dpdk.org>
Cc: <Ferruh.Yigit@amd.com>, Vipin Varghese <vipin.varghese@amd.com>
Subject: [PATCH] usertools: suggest use of hwloc for new cpu
Date: Sat, 12 Aug 2023 06:07:55 +0530	[thread overview]
Message-ID: <20230812003755.978-1-vipin.varghese@amd.com> (raw)

Most modern processor now supports numa partitioning using
sub NUMA CPU-IO & Last Level Cache within the same socket.
As per the discussion in mailing list, suggesting the make
use of hw-loc for such scenarios.

Signed-off-by: Vipin Varghese <vipin.varghese@amd.com>
---
---
 usertools/cpu_layout.py | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/usertools/cpu_layout.py b/usertools/cpu_layout.py
index 891b9238fa..48c1f06d95 100755
--- a/usertools/cpu_layout.py
+++ b/usertools/cpu_layout.py
@@ -29,6 +29,16 @@
         core_map[key] = []
     core_map[key].append(cpu)
 
+
+print("")
+print(format("=" * (55 + len(base_path))))
+print(" for more porcessors, which support sub Socket Numa & L3 Numa clustering, please use")
+print(format("=" * (55 + len(base_path))))
+print("  - lstopo-no-graphics  --no-io -.ascii (CPU Mapping)")
+print("  - lstopo-no-graphics  -.ascii --whole-io --no-caches (IO device Mapping)")
+print(format("=" * (55 + len(base_path))))
+print("")
+
 print(format("=" * (47 + len(base_path))))
 print("Core and Socket Information (as reported by '{}')".format(base_path))
 print("{}\n".format("=" * (47 + len(base_path))))
-- 
2.34.1


             reply	other threads:[~2023-08-12  0:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-12  0:37 Vipin Varghese [this message]
2023-08-12  0:57 Vipin Varghese
2023-08-12 15:00 ` Stephen Hemminger
2023-08-13  2:12   ` Varghese, Vipin
2023-08-13 15:52     ` Stephen Hemminger
2023-08-13 16:35       ` Varghese, Vipin
2023-08-14  8:52       ` Bruce Richardson
2023-08-14  9:13         ` Morten Brørup
2023-08-14  9:25         ` Konstantin Ananyev
2023-09-04 10:11           ` Ferruh Yigit
2023-09-04 10:20             ` Bruce Richardson
2023-09-04 13:22               ` 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=20230812003755.978-1-vipin.varghese@amd.com \
    --to=vipin.varghese@amd.com \
    --cc=Ferruh.Yigit@amd.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).