mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Reinette Chatre <reinette.chatre@intel.com>
To: Yury Norov <yury.norov@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>
Cc: James Morse <james.morse@arm.com>,
	Tony Luck <tony.luck@intel.com>,
	"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
	"H. Peter Anvin" <hpa@zytor.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] cpumask: add missing API and simplify cpumask_any_housekeeping()
Date: Fri, 2 May 2025 09:17:42 -0700	[thread overview]
Message-ID: <dccc8512-750d-4806-9c56-acbe9e3340a6@intel.com> (raw)
In-Reply-To: <aBTlh5RdqqyQbQFn@yury>

Dear x86 Maintainers,

On 5/2/25 8:32 AM, Yury Norov wrote:
> On Thu, May 01, 2025 at 03:06:18PM -0700, Reinette Chatre wrote:
>> Hi Yury,
>>
>> On 4/27/25 11:52 AM, Yury Norov wrote:
>>> From: Yury Norov [NVIDIA] <yury.norov@gmail.com>
>>>
>>> cpumask library missed some flavors of cpumask_any_but(), which makes
>>> users to workaround it by using less efficient cpumask_nth() functions
>>>
>>> This series adds missing cpumask_any_andnot_but() and makes
>>> cpumask_any_but() understanding the RESCTRL_PICK_ANY_CPU hint.
>>> This simplifies cpumask_any_housekeeping() significantly.
>>>
>>> v1: https://lore.kernel.org/all/20250407153856.133093-1-yury.norov@gmail.com/
>>> v2:
>>>  - switch cpumask_any_but() functions to signed type for CPU (Reinette);
>>>  - change name for the new function to cpumask_any_andnot_but() (James);
>>>  - drop O(n*log(n)) comment. cpumask_nth() is slower, but still linear.
>>>
>>> Yury Norov [NVIDIA] (4):
>>>   cpumask: relax cpumask_any_but()
>>>   find: add find_first_andnot_bit()
>>>   cpumask: add cpumask_{first,next}_andnot() API
>>>   x86/resctrl: optimize cpumask_any_housekeeping()
>>
>> Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
>>
>> Does anything in your "bitmap-for-next" branch depend on this
>> series? If not, would you be ok if this series goes upstream
>> via tip (pending confirmation from tip maintainers) to make
>> for smoother upstream of resctrl patches that touch the same area?
>  
> Sure, please take it with the resctrl material.
> 

Could you please consider this work for inclusion into tip's
x86/cache branch? 

Thank you very much.

Reinette

      reply	other threads:[~2025-05-02 16:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-27 18:52 Yury Norov
2025-04-27 18:52 ` [PATCH v2 1/4] cpumask: relax cpumask_any_but() Yury Norov
2025-04-27 18:52 ` [PATCH v2 2/4] find: add find_first_andnot_bit() Yury Norov
2025-04-27 18:52 ` [PATCH v2 3/4] cpumask: add cpumask_{first,next}_andnot() API Yury Norov
2025-04-27 18:52 ` [PATCH v2 4/4] x86/resctrl: Optimize cpumask_any_housekeeping() Yury Norov
2025-05-01 22:06 ` [PATCH v2 0/4] cpumask: add missing API and simplify cpumask_any_housekeeping() Reinette Chatre
2025-05-02 15:32   ` Yury Norov
2025-05-02 16:17     ` Reinette Chatre [this message]

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=dccc8512-750d-4806-9c56-acbe9e3340a6@intel.com \
    --to=reinette.chatre@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=james.morse@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=yury.norov@gmail.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

all inboxes | Powered by JetHome®