From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: David Laight <David.Laight@aculab.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"yury.norov@gmail.com" <yury.norov@gmail.com>,
"linux@rasmusvillemoes.dk" <linux@rasmusvillemoes.dk>,
"n26122115@gs.ncku.edu.tw" <n26122115@gs.ncku.edu.tw>,
"jserv@ccns.ncku.edu.tw" <jserv@ccns.ncku.edu.tw>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] lib/test_bitops: Add benchmark test for fns()
Date: Mon, 6 May 2024 01:27:21 +0800 [thread overview]
Message-ID: <ZjfBeUJDRMHJKQMX@visitorckw-System-Product-Name> (raw)
In-Reply-To: <44e9ab62e0f543439eb7566a9f134af6@AcuMS.aculab.com>
Hi David,
On Sun, May 05, 2024 at 01:03:23PM +0000, David Laight wrote:
> From: Kuan-Wei Chiu
> > Sent: 01 May 2024 08:17
> >
> > Introduce a benchmark test for the fns(). It measures the total time
> > taken by fns() to process 1,000,000 test data generated using
> > get_random_long() for each n in the range [0, BITS_PER_LONG).
> >
> > example:
> > test_bitops: fns: 5876762553 ns, 64000000 iterations
>
> Great benchmark....
>
> The compiler almost certainly optimises it all away.
>
> Assigning the result of fns() to a file scope (global) volatile int
> should stop that happening.
>
Thank you for your review. There is an updated v5 of this patch [1],
which has already been accepted and included in Yury's bitmap-for-next
branch of the bitmap tree. In the v5 patch, we have addressed the issue
you mentioned regarding the use of volatile variables to avoid compiler
optimizations.
> And a real test would actually check the result - just in case
> someone does something silly.
>
The fns() function is mainly a helper for find_nth_bit(), so its
accuracy should have been checked in find_nth_bit()'s tests. If you
want unit tests for fns() here too, that sounds good to me, but it
would likely be a separate patch. I'm happy to do it if you'd like.
Regards,
Kuan-Wei
> David
>
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
> Registration No: 1397386 (Wales)
>
next prev parent reply other threads:[~2024-05-05 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 7:16 [PATCH v3 0/2] bitops: Optimize fns() for improved performance Kuan-Wei Chiu
2024-05-01 7:16 ` [PATCH v3 1/2] lib/test_bitops: Add benchmark test for fns() Kuan-Wei Chiu
2024-05-05 13:03 ` David Laight
2024-05-05 17:27 ` Kuan-Wei Chiu [this message]
2024-05-05 17:29 ` Kuan-Wei Chiu
2024-05-01 7:16 ` [PATCH v3 2/2] bitops: Optimize fns() for improved performance Kuan-Wei Chiu
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=ZjfBeUJDRMHJKQMX@visitorckw-System-Product-Name \
--to=visitorckw@gmail.com \
--cc=David.Laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=jserv@ccns.ncku.edu.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=n26122115@gs.ncku.edu.tw \
--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