From: Stephen Hemminger <stephen@networkplumber.org>
To: "Varghese, Vipin" <Vipin.Varghese@amd.com>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>,
"Yigit, Ferruh" <Ferruh.Yigit@amd.com>
Subject: Re: [PATCH] usertools: suggest use of hwloc for new cpu
Date: Sun, 13 Aug 2023 08:52:01 -0700 [thread overview]
Message-ID: <20230813085201.719e7a73@hermes.local> (raw)
In-Reply-To: <MN2PR12MB30852A5C2671ECFCA217BF298216A@MN2PR12MB3085.namprd12.prod.outlook.com>
On Sun, 13 Aug 2023 02:12:03 +0000
"Varghese, Vipin" <Vipin.Varghese@amd.com> wrote:
> >
> > On Sat, 12 Aug 2023 06:27:20 +0530
> > Vipin Varghese <vipin.varghese@amd.com> wrote:
> >
> > > Most modern processor now supports numa by partitioning NUMA based on
> > > 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>
> >
> > NAK, no scripting hwloc, it is ugly and creates a dependency that is not listed
> > in DPDK packaging.
>
> There is no calls to hwloc within in thescript. Hence not clear what does ` NAK, no scripting hwloc it is ugly and creates a dependency that is not listed in DPDK packaging.`.
>
> Requesting to cross check why NAK is shared for `print` as suggestion. Hence, I have disagree to this.
Sorry, I misinterpreted what the print's were doing.
Better off not to list exact flags, the lstopo may change and user may want different
format anyway.
How about something like this?
doc/guides/rel_notes/deprecation.rst | 5 +++++
usertools/cpu_layout.py | 5 +++++
2 files changed, 10 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 317875c5054b..25a116900dfb 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -185,3 +185,8 @@ Deprecation Notices
will be deprecated and subsequently removed in DPDK 24.11 release.
Before this, the new port library API (functions rte_swx_port_*)
will gradually transition from experimental to stable status.
+
+* cpulayout: The CPU layout script is unable to deal with all the possible
+ complexities of modern CPU topology. Other existing tools offer more
+ features and do a better job with keeping up with innovations.
+ Therefore it will be deprecated and removed in a future release.
diff --git a/usertools/cpu_layout.py b/usertools/cpu_layout.py
index 891b9238fa19..37a4f9ff24b4 100755
--- a/usertools/cpu_layout.py
+++ b/usertools/cpu_layout.py
@@ -62,3 +62,8 @@
else:
output += " " * (max_core_map_len + 1)
print(output)
+
+print("")
+print("This tool is unable to cope with complex NUMA layouts")
+print("and will be removed in a future release.")
+print("Suggest using lstopo or similar tools instead.")
--
2.39.2
next prev parent reply other threads:[~2023-08-13 15:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 0:57 [PATCH] usertools: suggest use of hwloc for new cpu Vipin Varghese
2023-08-12 15:00 ` Stephen Hemminger
2023-08-13 2:12 ` Varghese, Vipin
2023-08-13 15:52 ` Stephen Hemminger [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2023-08-12 0:37 Vipin Varghese
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=20230813085201.719e7a73@hermes.local \
--to=stephen@networkplumber.org \
--cc=Ferruh.Yigit@amd.com \
--cc=Vipin.Varghese@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.