From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Yury Norov <yury.norov@gmail.com>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v3 0/6] lib: Extend bitmap find binary operations
Date: Mon, 2 Sep 2024 17:42:50 -0400 [thread overview]
Message-ID: <f0dbd190-df68-4b0e-963c-d6f7ada5dc77@efficios.com> (raw)
In-Reply-To: <ZtJPis2WKGgk9hvz@yury-ThinkPad>
On 2024-08-30 19:02, Yury Norov wrote:
> On Fri, Aug 30, 2024 at 03:10:37PM -0400, Mathieu Desnoyers wrote:
>> Extend bitmap find.h and cpumask.h with additional binary operations
>> such as "nor".
>>
>> Also extend the testing and benchmark coverage of those bitmap find with
>> binary operations.
>>
>> This is useful for NUMA-aware rseq concurrency IDs which depend on this
>> series. The series can be found at:
>>
>> https://lore.kernel.org/lkml/20240823185946.418340-1-mathieu.desnoyers@efficios.com/
>>
>
> Added in bitmap-for-next for testing.
Hi Yuri,
FYI, after a lot of performance results analysis on variations over
the NUMA-aware rseq patch, I figured I need to take a drastically
different (and much simpler) approach to solve this in order to improve
cache locality as well, and it turns out I likely won't need the new
bitwise ops added by this series.
So feel free to keep it as a general improvement, or to drop it for
now.
Thanks,
Mathieu
>
> Thanks,
> Yury
>
>>
>> Mathieu Desnoyers (6):
>> lib: Clarify comment on top of find_next_andnot_bit
>> lib: Implement find_{first,next,nth}_nor_bit, for_each_nor_bit,
>> find_first_andnot_bit
>> lib: test bitmap sets binary operation iterators
>> lib: Fix test_find_first_and_bit and test_find_next_and_bit benchmark
>> lib: benchmark bitmap sets binary operation find
>> cpumask: Implement cpumask_{first,next}_{nor,andnot}
>>
>> include/linux/cpumask.h | 60 ++++++++++++++++
>> include/linux/find.h | 124 +++++++++++++++++++++++++++++++--
>> lib/find_bit.c | 36 ++++++++++
>> lib/find_bit_benchmark.c | 143 +++++++++++++++++++++++++++++++++------
>> lib/test_bitmap.c | 81 ++++++++++++++++++++++
>> 5 files changed, 418 insertions(+), 26 deletions(-)
>>
>> --
>> 2.39.2
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
prev parent reply other threads:[~2024-09-02 21:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 19:10 Mathieu Desnoyers
2024-08-30 19:10 ` [PATCH v3 1/6] lib: Clarify comment on top of find_next_andnot_bit Mathieu Desnoyers
2024-08-30 19:10 ` [PATCH v3 2/6] lib: Implement find_{first,next,nth}_nor_bit, for_each_nor_bit, find_first_andnot_bit Mathieu Desnoyers
2024-08-30 19:10 ` [PATCH v3 3/6] lib: test bitmap sets binary operation iterators Mathieu Desnoyers
2024-08-30 19:10 ` [PATCH v3 4/6] lib: Fix test_find_first_and_bit and test_find_next_and_bit benchmark Mathieu Desnoyers
2024-08-30 19:10 ` [PATCH v3 5/6] lib: benchmark bitmap sets binary operation find Mathieu Desnoyers
2024-08-30 19:10 ` [PATCH v3 6/6] cpumask: Implement cpumask_{first,next}_{nor,andnot} Mathieu Desnoyers
2024-08-30 23:02 ` [PATCH v3 0/6] lib: Extend bitmap find binary operations Yury Norov
2024-09-02 21:42 ` Mathieu Desnoyers [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=f0dbd190-df68-4b0e-963c-d6f7ada5dc77@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=peterz@infradead.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®