From: Thomas Monjalon <thomas@monjalon.net>
To: Aman Kumar <aman.kumar@vvdntech.in>,
David Marchand <david.marchand@redhat.com>,
"Song, Keesang" <keesang.song@amd.com>,
techboard@dpdk.org
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] config/x86: add support for AMD platform
Date: Thu, 18 Nov 2021 13:25:38 +0100 [thread overview]
Message-ID: <4391381.llMs6SCV4p@thomas> (raw)
In-Reply-To: <1902057.C4l9sbjloW@thomas>
I request a techboard decision for this patch.
02/11/2021 20:04, Thomas Monjalon:
> 02/11/2021 19:45, David Marchand:
> > On Tue, Nov 2, 2021 at 3:53 PM Aman Kumar <aman.kumar@vvdntech.in> wrote:
> > >
> > > -Dcpu_instruction_set=znverX meson option can be used
> > > to build dpdk for AMD platforms. Supported options are
> > > znver1, znver2 and znver3.
> > >
> > > Signed-off-by: Aman Kumar <aman.kumar@vvdntech.in>
> > > ---
> > > dpdk_conf.set('RTE_CACHE_LINE_SIZE', 64)
> > > dpdk_conf.set('RTE_MAX_LCORE', 128)
> > > dpdk_conf.set('RTE_MAX_NUMA_NODES', 32)
> > > +
> > > +# AMD platform support
> > > +if get_option('cpu_instruction_set') == 'znver1'
> > > + dpdk_conf.set('RTE_MAX_LCORE', 256)
> > > +elif get_option('cpu_instruction_set') == 'znver2'
> > > + dpdk_conf.set('RTE_MAX_LCORE', 512)
> > > +elif get_option('cpu_instruction_set') == 'znver3'
> > > + dpdk_conf.set('RTE_MAX_LCORE', 512)
> > > +endif
> >
> > I already replied to a similar patch earlier in this release.
> > https://inbox.dpdk.org/dev/CAJFAV8z-5amvEnr3mazkTqH-7SZX_C6EqCua6UdMXXHgrcmT6g@mail.gmail.com/
> >
> > So repeating the same: do you actually _need_ more than 128 lcores in
> > a single DPDK application?
We did not receive an answer to this question.
> Yes I forgot this previous discussion concluding that we should not increase
> more than 128 threads.
We had a discussion yesterday in techboard meeting.
The consensus is that we didn't hear for real need of more than 128 threads,
except for configuration usability convenience.
Now looking again at the code, this is how it is defined:
option('max_lcores', type: 'string', value: 'default', description:
'Set maximum number of cores/threads supported by EAL;
"default" is different per-arch, "detect" detects the number of cores on the build machine.')
config/x86/meson.build: dpdk_conf.set('RTE_MAX_LCORE', 128)
config/ppc/meson.build: dpdk_conf.set('RTE_MAX_LCORE', 128)
config/arm/meson.build: it goes from 4 to 1280!
So I feel it is not fair to reject this AMD patch if we allow Arm to go beyond.
Techboard, let's have a quick decision please for 21.11-rc4.
> The --lcores syntax and David's work on rte_thread_register should unblock
> most of use cases.
next prev parent reply other threads:[~2021-11-18 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 14:52 Aman Kumar
2021-11-02 15:18 ` Thomas Monjalon
2021-11-02 15:56 ` Song, Keesang
2021-11-02 18:45 ` David Marchand
2021-11-02 19:04 ` Thomas Monjalon
2021-11-18 12:25 ` Thomas Monjalon [this message]
2021-11-18 13:52 ` Bruce Richardson
2021-11-18 14:05 ` Thomas Monjalon
2021-11-24 12:36 ` Thomas Monjalon
2021-12-17 20:12 ` Song, Keesang
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=4391381.llMs6SCV4p@thomas \
--to=thomas@monjalon.net \
--cc=aman.kumar@vvdntech.in \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=keesang.song@amd.com \
--cc=techboard@dpdk.org \
/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).