From: David Laight <David.Laight@ACULAB.COM>
To: 'Kuan-Wei Chiu' <visitorckw@gmail.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"yury.norov@gmail.com" <yury.norov@gmail.com>
Cc: "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: Sun, 5 May 2024 13:03:23 +0000 [thread overview]
Message-ID: <44e9ab62e0f543439eb7566a9f134af6@AcuMS.aculab.com> (raw)
In-Reply-To: <20240501071647.10228-2-visitorckw@gmail.com>
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.
And a real test would actually check the result - just in case
someone does something silly.
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 13:04 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 [this message]
2024-05-05 17:27 ` Kuan-Wei Chiu
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=44e9ab62e0f543439eb7566a9f134af6@AcuMS.aculab.com \
--to=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=visitorckw@gmail.com \
--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®