From: Nole Zhang <peng.zhang@corigine.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Nole Zhang <peng.zhang@corigine.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Chaoyong He <chaoyong.he@corigine.com>,
oss-drivers <oss-drivers@corigine.com>
Subject: RE: FW: [PATCH v1] buildtools: ensure the NUMA nodes are counted correct
Date: Wed, 21 Sep 2022 07:19:15 +0000 [thread overview]
Message-ID: <BL0PR13MB44509C515858BBDDB19536B6EF4F9@BL0PR13MB4450.namprd13.prod.outlook.com> (raw)
In-Reply-To: <4213175.ejJDZkT8p0@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: 2022年9月20日 21:23
> To: Niklas Soderlund <niklas.soderlund@corigine.com>
> Cc: Nole Zhang <peng.zhang@corigine.com>; dev@dpdk.org; Chaoyong He
> <chaoyong.he@corigine.com>; oss-drivers <oss-drivers@corigine.com>
> Subject: Re: FW: [PATCH v1] buildtools: ensure the NUMA nodes are counted
> correct
>
> Hi,
>
> 20/09/2022 12:11, Niklas Soderlund:
> > Hi Thomas,
> >
> > Have you checked if this address the same issue you where seeing? Do
> > you think we can move forward with this fix?
>
> Yes. No need to show lscpu output,
> but the output of the DPDK initialization would be more interesting.
>
OK, this is the DPDK initialization.
The original code, the dpdkd initialized info:
EAL: Detected CPU lcores: 128
EAL: Detected NUMA nodes: 10
EAL: Static memory layout is selected, amount of reserved memory can be adjusted with -m or --socket-mem
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
Revised code, the dpdkd initialized info:
EAL: Detected CPU lcores: 128
EAL: Detected NUMA nodes: 16
EAL: Static memory layout is selected, amount of reserved memory can be adjusted with -m or --socket-mem
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
>
> > On 2022-08-31 10:47:24 +0200, Nole Zhang wrote:
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Thomas Monjalon <thomas@monjalon.net>
> > > > Sent: 2022年8月29日 21:15
> > > > To: Nole Zhang <peng.zhang@corigine.com>; Chaoyong He
> > > > <chaoyong.he@corigine.com>
> > > > Subject: Re: [PATCH v1] buildtools: ensure the NUMA nodes are
> > > > counted correct
> > > >
> > > > 29/08/2022 13:17, Nole Zhang:
> > > > > From: Thomas Monjalon <thomas@monjalon.net>
> > > > > > 02/08/2022 09:54, Chaoyong He:
> > > > > > > From: Peng Zhang <peng.zhang@corigine.com>
> > > > > > >
> > > > > > > Sorting a list of strings with the format "node[0-9]+" in
> > > > > > > order to find the largest integer by looking at the last
> > > > > > > item after the sort breaks. But if there are more then 10
> > > > > > > items as a string sort will sort "node10" before "node2", it will get
> the error NUMA nodes.
> > > > > >
> > > > > > What is the error you are seeing?
> > > > > >
> > > > > >
> > > > > We get the error NUMA, in this example, we get the NUMA nodes is
> > > > > 10, But at fact, it has 11 NUMA.
> > > >
> > > > Please give more details, where do you see this error?
> > > > We should know how to reproduce and check we have the same issue.
> > > > Thanks
> > > >
> > > > Please reply with a detailed answer on the mailing list.
> > > >
> > > In the China Phytium S2500 CPU + INSPUR server, it has 16 NUMA.
> > > The details are as follows:
> > >
> > > ~#: lscpu
> > >
> > > Architecture: aarch64
> > > CPU op-mode(s): 64-bit
> > > Byte Order: Little Endian
> > > CPU(s): 128
> > > On-line CPU(s) list: 0-127
> > > Thread(s) per core: 1
> > > Core(s) per socket: 64
> > > Socket(s): 2
> > > NUMA node(s): 16
> > > Vendor ID: 0x70
> > > Model: 3
> > > Model name: S2500
> > > Stepping: 0x1
> > > BogoMIPS: 100.00
> > > L1d cache: 4 MiB
> > > L1i cache: 4 MiB
> > > L2 cache: 64 MiB
> > > L3 cache: 128 MiB
> > > NUMA node0 CPU(s): 0-7
> > > NUMA node1 CPU(s): 8-15
> > > NUMA node2 CPU(s): 16-23
> > > NUMA node3 CPU(s): 24-31
> > > NUMA node4 CPU(s): 32-39
> > > NUMA node5 CPU(s): 40-47
> > > NUMA node6 CPU(s): 48-55
> > > NUMA node7 CPU(s): 56-63
> > > NUMA node8 CPU(s): 64-71
> > > NUMA node9 CPU(s): 72-79
> > > NUMA node10 CPU(s): 80-87
> > > NUMA node11 CPU(s): 88-95
> > > NUMA node12 CPU(s): 96-103
> > > NUMA node13 CPU(s): 104-111
> > > NUMA node14 CPU(s): 112-119
> > > NUMA node15 CPU(s): 120-127
> > > Flags: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
> lpae evtstrm
> > >
> > >
> > > I use meson build -Dmax_lcores=detect -Dmax_numa_nodes=detect to
> compile, then dpdk initialization only shows 10 numa.
> >
> >
>
>
>
>
next prev parent reply other threads:[~2022-09-21 7:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 7:54 Chaoyong He
2022-08-29 10:41 ` Thomas Monjalon
[not found] ` <MWHPR1301MB1997EA5A5CF4A320A13493E4EF769@MWHPR1301MB1997.namprd13.prod.outlook.com>
[not found] ` <3155813.0WQXIW03uk@thomas>
[not found] ` <MWHPR1301MB1997910EB07FA86DE33053C2EF799@MWHPR1301MB1997.namprd13.prod.outlook.com>
2022-08-31 8:47 ` FW: " Nole Zhang
2022-09-20 10:11 ` Niklas Soderlund
2022-09-20 13:22 ` Thomas Monjalon
2022-09-21 7:19 ` Nole Zhang [this message]
2022-09-21 8:07 ` Thomas Monjalon
2022-09-22 8:06 ` [PATCH v2] " Niklas Söderlund
2022-10-10 7:52 ` Niklas Söderlund
2022-10-10 23:11 ` 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=BL0PR13MB44509C515858BBDDB19536B6EF4F9@BL0PR13MB4450.namprd13.prod.outlook.com \
--to=peng.zhang@corigine.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=oss-drivers@corigine.com \
--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).