From: Thomas Monjalon <thomas@monjalon.net>
To: Ruifeng Wang <Ruifeng.Wang@arm.com>, Jerin Jacob <jerinjacobk@gmail.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
Jan Viktorin <viktorin@rehivetech.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
nd <nd@arm.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Subject: Re: [dpdk-dev] [PATCH v4 3/3] build: add option to enable wait until equal
Date: Thu, 08 Jul 2021 09:32:57 +0200 [thread overview]
Message-ID: <4337273.iQpEcjLWDA@thomas> (raw)
In-Reply-To: <CALBAE1NzutaQ421q173H4B1iXOL3C2tuBhT2RWRP4Cv3cUK8DQ@mail.gmail.com>
08/07/2021 08:32, Jerin Jacob:
> On Thu, Jul 8, 2021 at 11:55 AM Ruifeng Wang <Ruifeng.Wang@arm.com> wrote:
> > From: Jerin Jacob <jerinjacobk@gmail.com>
> > > On Wed, Jul 7, 2021 at 5:57 PM Bruce Richardson
> > > <bruce.richardson@intel.com> wrote:
> > > > On Wed, Jul 07, 2021 at 06:46:33AM +0000, Ruifeng Wang wrote:
> > > > > From: Thomas Monjalon <thomas@monjalon.net>
> > > > > > 07/07/2021 07:48, Ruifeng Wang:
> > > > > > > Introduce a meson option 'use_wfe' to select wait until equal method.
> > > > > > > The default is disable. Traditional polling loop is used.
> > > > > > > When enabled, architecture specific mechanism is relied on to do
> > > > > > > the wait.
> > > > > >
> > > > > > Why do we need an option?
> > > > > > Can it be automatic to enable it when supported?
> > > > > >
> > > > > The problem is inconsistency in performance on different Arm platforms.
> > > We had decided that each platform needs to enable it after some testing.
> > > > >
> > > > Can that not be done via variables in the cross-file for the builds,
> > > > or via automatic detection if it's a native build? Is it likely that
> > > > individual users of DPDK will be knowledgable enough to use this option
> > > correctly?
> > >
> > > +1 to add this in cross-file instead of the top of config option as
> > > scope if is only for arm64 builds.
> >
> > Currently this option is in config/arm/meson.build (flags_common). SoCs can build
> > with this option enabled/disabled. And the ability is available for both native build
> > and cross build as cross build also goes through meson.build.
> > If a SoC needs to enable the option by default, an entry and be added to the SoC flags.
> >
> > The key difference here is whether this option need to be exposed to the top level config.
>
> In the view of limiting top-level config options and it is specific to
> Arm, I think, it better to
> be a cross file only option.
+1, sorry for the late notice.
I would advocate to take this patch in 21.08-rc2.
next prev parent reply other threads:[~2021-07-08 7:33 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 7:07 [dpdk-dev] [PATCH v1 0/2] Use WFE for spinlock and ring Gavin Hu
2020-04-24 7:07 ` [dpdk-dev] [PATCH v1 1/2] spinlock: use wfe to reduce contention on aarch64 Gavin Hu
2020-04-24 7:07 ` [dpdk-dev] [PATCH v1 2/2] ring: use wfe to wait for ring tail update " Gavin Hu
2020-04-24 13:23 ` Ananyev, Konstantin
2020-04-26 8:41 ` Gavin Hu
2020-04-24 14:46 ` Honnappa Nagarahalli
2020-04-26 8:33 ` Gavin Hu
2020-04-26 8:39 ` [dpdk-dev] [PATCH v2 0/2] Use WFE for spinlock and ring Gavin Hu
2020-05-01 9:47 ` Ananyev, Konstantin
2020-05-03 14:54 ` David Marchand
2020-05-03 21:31 ` Honnappa Nagarahalli
2020-09-25 14:30 ` David Marchand
2021-03-25 14:58 ` David Marchand
2021-04-25 6:06 ` Ruifeng Wang
2021-04-25 15:56 ` Thomas Monjalon
2020-04-26 8:39 ` [dpdk-dev] [PATCH v2 1/2] spinlock: use wfe to reduce contention on aarch64 Gavin Hu
2020-04-28 12:22 ` Jerin Jacob
2020-04-26 8:39 ` [dpdk-dev] [PATCH v2 2/2] ring: use wfe to wait for ring tail update " Gavin Hu
2021-04-25 5:56 ` [dpdk-dev] Use WFE for spinlock and ring Ruifeng Wang
2021-04-25 5:56 ` [dpdk-dev] [PATCH v3 1/2] spinlock: use wfe to reduce contention on aarch64 Ruifeng Wang
2021-04-25 5:56 ` [dpdk-dev] [PATCH v3 2/2] ring: use wfe to wait for ring tail update " Ruifeng Wang
2021-04-26 5:38 ` Jerin Jacob
2021-04-28 17:17 ` Stephen Hemminger
2021-04-29 14:35 ` Ruifeng Wang
2021-04-29 15:05 ` Stephen Hemminger
2021-05-07 8:25 ` Ruifeng Wang
2021-04-28 7:42 ` [dpdk-dev] Use WFE for spinlock and ring David Marchand
2021-04-28 9:30 ` Ruifeng Wang
2021-04-28 11:13 ` Thomas Monjalon
2021-04-29 14:28 ` Ruifeng Wang
2021-04-29 15:20 ` Thomas Monjalon
2021-04-30 9:16 ` Bruce Richardson
2021-04-30 13:41 ` Honnappa Nagarahalli
2021-04-30 14:19 ` Bruce Richardson
2021-05-07 10:18 ` Ruifeng Wang
2021-05-07 10:24 ` Bruce Richardson
2021-07-05 8:51 ` David Marchand
2021-07-05 10:21 ` Ruifeng Wang
2021-07-07 14:47 ` Stephen Hemminger
2021-07-08 9:41 ` Ruifeng Wang
2021-07-08 16:58 ` Honnappa Nagarahalli
2021-07-07 5:43 ` [dpdk-dev] [PATCH v4 0/3] " Ruifeng Wang
2021-07-07 5:43 ` [dpdk-dev] [PATCH v4 1/3] spinlock: use wfe to reduce contention on aarch64 Ruifeng Wang
2021-07-07 5:43 ` [dpdk-dev] [PATCH v4 2/3] ring: use wfe to wait for ring tail update " Ruifeng Wang
2021-07-07 5:43 ` [dpdk-dev] [PATCH v4 3/3] build: add option to enable wait until equal Ruifeng Wang
2021-07-07 12:15 ` David Marchand
2021-07-07 5:48 ` [dpdk-dev] [PATCH v4 0/3] Use WFE for spinlock and ring Ruifeng Wang
2021-07-07 5:48 ` [dpdk-dev] [PATCH v4 1/3] spinlock: use wfe to reduce contention on aarch64 Ruifeng Wang
2021-07-07 5:48 ` [dpdk-dev] [PATCH v4 2/3] ring: use wfe to wait for ring tail update " Ruifeng Wang
2021-07-07 5:48 ` [dpdk-dev] [PATCH v4 3/3] build: add option to enable wait until equal Ruifeng Wang
2021-07-07 6:32 ` Thomas Monjalon
2021-07-07 6:46 ` Ruifeng Wang
2021-07-07 12:27 ` Bruce Richardson
2021-07-07 12:36 ` Jerin Jacob
2021-07-08 6:25 ` Ruifeng Wang
2021-07-08 6:32 ` Jerin Jacob
2021-07-08 7:32 ` Thomas Monjalon [this message]
2021-07-08 9:21 ` Ruifeng Wang
2021-07-08 10:28 ` Thomas Monjalon
2021-07-09 18:39 ` [dpdk-dev] [PATCH v4 0/3] Use WFE for spinlock and ring 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=4337273.iQpEcjLWDA@thomas \
--to=thomas@monjalon.net \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=nd@arm.com \
--cc=viktorin@rehivetech.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).