From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: akpm@linux-foundation.org, yury.norov@gmail.com
Cc: linux@rasmusvillemoes.dk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] bitops: Optimize fns() for improved performance
Date: Tue, 30 Apr 2024 14:11:45 +0800 [thread overview]
Message-ID: <ZjCLoeFE6xoNaRWt@visitorckw-System-Product-Name> (raw)
In-Reply-To: <20240430054912.124237-1-visitorckw@gmail.com>
On Tue, Apr 30, 2024 at 01:49:10PM +0800, Kuan-Wei Chiu wrote:
> Hello,
>
> This patch series optimizes the fns() function by avoiding repeated
> calls to __ffs(). Additionally, tests for fns() have been added in
> lib/find_bit_benchmark.c.
>
> Changes in v2:
> - Add benchmark test for fns() in lib/find_bit_benchmark.c.
> - Change the loop in fns() by counting down from n to 0.
> - Add find_bit benchmark result for find_nth_bit in commit message.
>
> Link to v1: https://lkml.kernel.org/20240406235532.613696-1-visitorckw@gmail.com
Sorry for pasting the wrong link, the link to v1 should be:
https://lkml.kernel.org/20240426035152.956702-1-visitorckw@gmail.com
Regards,
Kuan-Wei
>
> Kuan-Wei Chiu (2):
> lib/find_bit_benchmark: Add benchmark test for fns()
> bitops: Optimize fns() for improved performance
>
> include/linux/bitops.h | 12 +++---------
> lib/find_bit_benchmark.c | 25 +++++++++++++++++++++++++
> 2 files changed, 28 insertions(+), 9 deletions(-)
>
> --
> 2.34.1
>
prev parent reply other threads:[~2024-04-30 6:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 5:49 [PATCH v2 0/2] bitops: Optimize fns() for improved performance Kuan-Wei Chiu
2024-04-30 5:49 ` [PATCH v2 1/2] lib/find_bit_benchmark: Add benchmark test for fns() Kuan-Wei Chiu
2024-04-30 17:24 ` Yury Norov
2024-05-01 4:50 ` Kuan-Wei Chiu
2024-04-30 22:50 ` kernel test robot
2024-04-30 5:49 ` [PATCH v2 2/2] bitops: Optimize fns() for improved performance Kuan-Wei Chiu
2024-04-30 17:36 ` Yury Norov
2024-04-30 6:11 ` Kuan-Wei Chiu [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=ZjCLoeFE6xoNaRWt@visitorckw-System-Product-Name \
--to=visitorckw@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.