From: Yury Norov <yury.norov@gmail.com>
To: Alexander Potapenko <glider@google.com>
Cc: catalin.marinas@arm.com, will@kernel.org, pcc@google.com,
andreyknvl@gmail.com, andriy.shevchenko@linux.intel.com,
aleksander.lobakin@intel.com, linux@rasmusvillemoes.dk,
alexandru.elisei@arm.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, eugenis@google.com,
syednwaris@gmail.com, william.gray@linaro.org
Subject: Re: [PATCH v10-mte 2/7] lib/test_bitmap: add tests for bitmap_{read,write}()
Date: Thu, 14 Dec 2023 11:50:33 -0800 [thread overview]
Message-ID: <ZXtciaxTKFBiui/X@yury-ThinkPad> (raw)
In-Reply-To: <20231214110639.2294687-3-glider@google.com>
On Thu, Dec 14, 2023 at 12:06:34PM +0100, Alexander Potapenko wrote:
> Add basic tests ensuring that values can be added at arbitrary positions
> of the bitmap, including those spanning into the adjacent unsigned
> longs.
>
> Two new performance tests, test_bitmap_read_perf() and
> test_bitmap_write_perf(), can be used to assess future performance
> improvements of bitmap_read() and bitmap_write():
>
> [ 0.431119][ T1] test_bitmap: Time spent in test_bitmap_read_perf: 615253
> [ 0.433197][ T1] test_bitmap: Time spent in test_bitmap_write_perf: 916313
>
> (numbers from a Intel(R) Xeon(R) Gold 6154 CPU @ 3.00GHz machine running
> QEMU).
>
> Signed-off-by: Alexander Potapenko <glider@google.com>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Acked-by: Yury Norov <yury.norov@gmail.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-12-14 19:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 11:06 [PATCH v10-mte 0/7] Implement MTE tag compression for swapped pages Alexander Potapenko
2023-12-14 11:06 ` [PATCH v10-mte 1/7] lib/bitmap: add bitmap_{read,write}() Alexander Potapenko
2023-12-14 19:48 ` Yury Norov
2023-12-14 11:06 ` [PATCH v10-mte 2/7] lib/test_bitmap: add tests for bitmap_{read,write}() Alexander Potapenko
2023-12-14 19:50 ` Yury Norov [this message]
2023-12-14 11:06 ` [PATCH v10-mte 3/7] lib/test_bitmap: use pr_info() for non-error messages Alexander Potapenko
2023-12-14 19:51 ` Yury Norov
2023-12-14 11:06 ` [PATCH v10-mte 4/7] arm64: mte: implement CONFIG_ARM64_MTE_COMP Alexander Potapenko
2023-12-14 20:16 ` Yury Norov
2023-12-15 15:19 ` Alexander Potapenko
2023-12-15 16:35 ` Yury Norov
2023-12-15 17:01 ` Yury Norov
2023-12-18 11:42 ` Alexander Potapenko
2023-12-18 11:45 ` Alexander Potapenko
2023-12-14 11:06 ` [PATCH v10-mte 5/7] arm64: mte: add a test for MTE tags compression Alexander Potapenko
2023-12-14 11:06 ` [PATCH v10-mte 6/7] arm64: mte: add compression support to mteswap.c Alexander Potapenko
2023-12-14 11:06 ` [PATCH v10-mte 7/7] arm64: mte: implement CONFIG_ARM64_MTE_SWAP_STATS Alexander Potapenko
2023-12-14 20:21 ` Yury Norov
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=ZXtciaxTKFBiui/X@yury-ThinkPad \
--to=yury.norov@gmail.com \
--cc=aleksander.lobakin@intel.com \
--cc=alexandru.elisei@arm.com \
--cc=andreyknvl@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=eugenis@google.com \
--cc=glider@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pcc@google.com \
--cc=syednwaris@gmail.com \
--cc=will@kernel.org \
--cc=william.gray@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).