DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Wenzhuo Lu <wenzhuo.lu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] usertools: enhance CPU layout
Date: Tue, 18 Apr 2023 09:46:46 -0700	[thread overview]
Message-ID: <20230418094646.799b2fc3@hermes.local> (raw)
In-Reply-To: <1681795541-68384-1-git-send-email-wenzhuo.lu@intel.com>

On Tue, 18 Apr 2023 13:25:41 +0800
Wenzhuo Lu <wenzhuo.lu@intel.com> wrote:

> The cores in a single CPU may be not all
> the same.
> The user tool is updated to show the
> difference of the cores.
> 
> This patch addes below informantion,
> 1, Group the cores based on the die.
> 2, A core is either a performance core or an
>    efficency core.
>    A performance core is shown as 'Core-P'.
>    An efficency core is shown as 'Core-E'.
> 3, All the E-cores which share the same L2-cache
>    are grouped to one module.
> 
> The known limitation.
> 1, To tell a core is P-core or E-core is based on if
>    this core shares L2 cache with others.
> 
> Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com>

Side note:
This tool only exists because of lack of simple tool at the time.
Looking around, found that there is a tool 'lstopo' under the hwloc
package that gives output in many formats including graphical and
seems to do a better job than the DPDK python script.

Not sure how much farther DPDK should go in this area?
Really should be a distro tool.

  parent reply	other threads:[~2023-04-18 16:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18  5:25 Wenzhuo Lu
2023-04-18 16:31 ` Stephen Hemminger
2023-04-18 16:46 ` Stephen Hemminger [this message]
2023-04-21  1:47   ` Lu, Wenzhuo
2023-04-21  8:28     ` Thomas Monjalon
2023-04-21 15:15       ` Stephen Hemminger
2023-04-24 17:05         ` Brice Goglin
2023-04-25  5:29           ` Lu, Wenzhuo

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=20230418094646.799b2fc3@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=wenzhuo.lu@intel.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).