From: Yury Norov <yury.norov@gmail.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [PATCH v3 2/7] lib/group_cpus: optimize inner loop in grp_spread_init_one()
Date: Mon, 25 Dec 2023 09:38:15 -0800 [thread overview]
Message-ID: <ZYm+B2m9gOTLOedE@yury-ThinkPad> (raw)
In-Reply-To: <ZXj1mGAKz5cWy+Nr@fedora>
On Wed, Dec 13, 2023 at 08:06:48AM +0800, Ming Lei wrote:
> On Tue, Dec 12, 2023 at 09:04:19AM -0800, Yury Norov wrote:
> > On Tue, Dec 12, 2023 at 05:46:53PM +0800, Ming Lei wrote:
> > > On Mon, Dec 11, 2023 at 08:21:02PM -0800, Yury Norov wrote:
> > > > The loop starts from the beginning every time we switch to the next
> > > > sibling mask. This is the Schlemiel the Painter's style of coding
> > > > because we know for sure that nmsk is clear up to current CPU, and we
> > > > can just continue from the next CPU.
> > > >
> > > > Also, we can do it nicer if leverage the dedicated for_each() iterator,
> > > > and simplify the logic of clearing a bit in nmsk.
> > > >
> > > > Signed-off-by: Yury Norov <yury.norov@gmail.com>
> > > > ---
> > > > lib/group_cpus.c | 13 ++++++-------
> > > > 1 file changed, 6 insertions(+), 7 deletions(-)
> > > >
> > > > diff --git a/lib/group_cpus.c b/lib/group_cpus.c
> > > > index ee272c4cefcc..10dead3ab0e0 100644
> > > > --- a/lib/group_cpus.c
> > > > +++ b/lib/group_cpus.c
> > > > @@ -30,14 +30,13 @@ static void grp_spread_init_one(struct cpumask *irqmsk, struct cpumask *nmsk,
> > > >
> > > > /* If the cpu has siblings, use them first */
> > > > siblmsk = topology_sibling_cpumask(cpu);
> > > > - for (sibl = -1; cpus_per_grp > 0; ) {
> > > > - sibl = cpumask_next(sibl, siblmsk);
> > > > - if (sibl >= nr_cpu_ids)
> > > > - break;
> > > > - if (!cpumask_test_and_clear_cpu(sibl, nmsk))
> > > > - continue;
> > > > + sibl = cpu + 1;
> > >
> > > It doesn't have to 'cpu + 1', see below comment.
> > >
> > > > +
> > > > + for_each_cpu_and_from(sibl, siblmsk, nmsk) {
> > > > + cpumask_clear_cpu(sibl, nmsk);
> > > > cpumask_set_cpu(sibl, irqmsk);
> > > > - cpus_per_grp--;
> > > > + if (cpus_per_grp-- == 0)
> > >
> > > if (--cpus_per_grp == 0)
> >
> > That's right, I'll send a new version this weekend.
> >
> > > > + return;
> > >
> > > I think for_each_cpu_and() should work just fine, cause cpu has been cleared
> > > from nmsk, so the change can be something like, then patch 1 isn't
> > > necessary.
> >
> > It works just fine except that it's O(N^2), where O(N) is easily
> > achievable. Again, it's not about performance, it's about coding
> > habits.
>
> Both for_each_cpu_and() and for_each_cpu_and_from() are O(N), aren't
> they? Given both two are based on find_next_and_bit().
for_each_cpu_and() is the same Schlemiel the Painter's code, as the
plain for() was.
> for_each_cpu_and() is simpler and more readable, and more
> importantly, we can save one single-user public helper.
>
> >
> > > for_each_cpu_and(sibl, siblmsk, nmsk) {
> > > cpumask_clear_cpu(sibl, nmsk);
> > > cpumask_set_cpu(sibl, irqmsk);
> > > if (--cpus_per_grp == 0)
> > > return;
> > > }
>
>
> Thanks,
> Ming
next prev parent reply other threads:[~2023-12-25 17:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 4:21 [PATCH v3 0/7] lib/group_cpus: rework grp_spread_init_one() and make it O(1) Yury Norov
2023-12-12 4:21 ` [PATCH v3 1/7] cpumask: introduce for_each_cpu_and_from() Yury Norov
2023-12-12 4:21 ` [PATCH v3 2/7] lib/group_cpus: optimize inner loop in grp_spread_init_one() Yury Norov
2023-12-12 9:46 ` Ming Lei
2023-12-12 17:04 ` Yury Norov
2023-12-13 0:06 ` Ming Lei
2023-12-25 17:38 ` Yury Norov [this message]
2023-12-12 4:21 ` [PATCH v3 3/7] lib/group_cpus: relax atomicity requirement " Yury Norov
2023-12-12 9:50 ` Ming Lei
2023-12-12 16:52 ` Yury Norov
2023-12-13 0:14 ` Ming Lei
2023-12-13 17:03 ` Yury Norov
2023-12-14 0:43 ` Ming Lei
2023-12-12 4:21 ` [PATCH v3 4/7] lib/group_cpus: optimize outer loop " Yury Norov
2023-12-12 4:21 ` [PATCH v3 5/7] lib/cgroup_cpus: don't zero cpumasks in group_cpus_evenly() on allocation Yury Norov
2023-12-13 0:56 ` Ming Lei
2023-12-12 4:21 ` [PATCH v3 6/7] lib/group_cpus: drop unneeded cpumask_empty() call in __group_cpus_evenly() Yury Norov
2023-12-13 0:59 ` Ming Lei
2023-12-12 4:21 ` [PATCH v3 7/7] lib/group_cpus: simplify grp_spread_init_one() for more Yury Norov
2023-12-13 1:06 ` Ming Lei
2023-12-25 18:03 ` Yury Norov
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=ZYm+B2m9gOTLOedE@yury-ThinkPad \
--to=yury.norov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=ming.lei@redhat.com \
--cc=tglx@linutronix.de \
/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