mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yury Norov <yury.norov@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] improve group_cpus initialization routines
Date: Thu, 27 Nov 2025 21:25:29 -0500	[thread overview]
Message-ID: <aSkIGTHGmzc8gw0A@yury> (raw)
In-Reply-To: <20251119031306.644129-1-yury.norov@gmail.com>

Ping?

On Tue, Nov 18, 2025 at 10:13:02PM -0500, Yury Norov (NVIDIA) wrote:
> Add missing core API and improve cpumasks usage in the initialization
> code.
> 
> Yury Norov (NVIDIA) (3):
>   bitmap: cpumask: introduce and_andnot search helper and iterator
>   group_cpus: don't call cpumask_weight() prematurely
>   group_cpus: simplify inner loop in grp_spread_init_one()
> 
>  include/linux/cpumask.h | 22 +++++++++++++++++++++
>  include/linux/find.h    | 38 +++++++++++++++++++++++++++++++++++++
>  lib/find_bit.c          |  9 +++++++++
>  lib/group_cpus.c        | 42 ++++++++++++-----------------------------
>  4 files changed, 81 insertions(+), 30 deletions(-)
> 
> -- 
> 2.43.0

  parent reply	other threads:[~2025-11-28  2:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19  3:13 Yury Norov (NVIDIA)
2025-11-19  3:13 ` [PATCH 1/3] bitmap: cpumask: introduce and_andnot search helper and iterator Yury Norov (NVIDIA)
2025-11-19  3:13 ` [PATCH 2/3] group_cpus: don't call cpumask_weight() prematurely Yury Norov (NVIDIA)
2025-11-19  3:13 ` [PATCH 3/3] group_cpus: simplify inner loop in grp_spread_init_one() Yury Norov (NVIDIA)
2025-11-28  2:25 ` Yury Norov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-09-10 21:08 [PATCH 0/3] improve group_cpus initialization routines 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=aSkIGTHGmzc8gw0A@yury \
    --to=yury.norov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --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

all inboxes | Powered by JetHome®