[AMD Official Use Only - General]

@Yigit, Ferruh thanks for bringing this to my attention,

The output of the modified

```
Socket 0   Numa 0
-------------------
Core 0      [0, 128]
Core 1      [1, 129]
Core 2      [2, 130]
Core 3      [3, 131]
.....
Core 29     [29, 157]
Core 30     [30, 158]
Core 31     [31, 159]

 Socket 0   Numa 1
-------------------
Core 0      [32, 160]
Core 1      [33, 161]
Core 2      [34, 162]
Core 3      [35, 163]
.....
Core 30     [62, 190]
Core 31     [63, 191]

 Socket 1   Numa 2
-------------------
Core 0      [64, 192]
Core 1      [65, 193]
Core 2      [66, 194]
Core 3      [67, 195]
.....
Core 31     [95, 223]

 Socket 1   Numa 3
-------------------
Core 0      [96, 224]
Core 1      [97, 225]
Core 2      [98, 226]
.....
Core 29     [125, 253]
Core 30     [126, 254]
Core 31     [127, 255]
```

The intention of the changes is clearly highlighted the NUMA divisioning and 
CPU pinning within single or multiple sockets. But as pointed out @Dmitry 
Kozlyuk if the end user will use hwloc on both linux & windows to identify 
these, we should promote and document the changes provided the existing tool is 
phased out.

Note: there were questions asked in forums, stackoverflow and github on NUMA to 
CPU pinning, hence enhanced the tool to accommodate the changes.

> -----Original Message-----
> From: Thomas Monjalon <tho...@monjalon.net>
> Sent: Wednesday, June 14, 2023 8:00 PM
> To: Yigit, Ferruh <ferruh.yi...@amd.com>
> Cc: Varghese, Vipin <vipin.vargh...@amd.com>; Dmitry Kozlyuk
> <dmitry.kozl...@gmail.com>; david.march...@redhat.com; Tummala,
> Sivaprasad <sivaprasad.tumm...@amd.com>; dev@dpdk.org; Narcisa Ana
> Maria Vasile <navas...@linux.microsoft.com>; Dmitry Malloy
> <dmit...@microsoft.com>; Pallavi Kadam <pallavi.ka...@intel.com>
> Subject: Re: [PATCH] usertools: enhance logic to display NUMA
>
> Caution: This message originated from an External Source. Use proper
> caution when opening attachments, clicking links, or responding.
>
>
> 14/06/2023 12:48, Ferruh Yigit:
> > Should we document preferred tool and usage in DPDK, if so where is
> > good location for it?
>
> I think it should be in the user guide.
> We are starting to merge the 3 user guides in 1.
> You can add it to the Linux guide only for now.
>
>

Reply via email to