From: Adrian Huang12 <ahuang12@lenovo.com>
To: "Uladzislau Rezki (Sony)" <urezki@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>, Baoquan He <bhe@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>
Subject: RE: [PATCH 1/4] lib/test_vmalloc.c: Replace RWSEM to SRCU for setup
Date: Thu, 24 Apr 2025 13:35:29 +0000 [thread overview]
Message-ID: <TYZPR03MB6192BA354C0B1DE09AF1D184B3852@TYZPR03MB6192.apcprd03.prod.outlook.com> (raw)
In-Reply-To: <20250417161216.88318-1-urezki@gmail.com>
> -----Original Message-----
> From: owner-linux-mm@kvack.org <owner-linux-mm@kvack.org> On Behalf
> Of Uladzislau Rezki (Sony)
> Sent: Friday, April 18, 2025 12:12 AM
> To: Andrew Morton <akpm@linux-foundation.org>
> Cc: linux-mm@kvack.org; LKML <linux-kernel@vger.kernel.org>; Baoquan He
> <bhe@redhat.com>; Christoph Hellwig <hch@infradead.org>; Uladzislau Rezki
> <urezki@gmail.com>; Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>
> Subject: [External] [PATCH 1/4] lib/test_vmalloc.c: Replace RWSEM to SRCU for
> setup
>
> The test has the initialization step during which threads are created. To
> prevent the workers from starting prematurely a write lock was previously
> used by the main setup thread, while each worker would block on a read lock.
>
> Replace this RWSEM based synchronization with a simpler SRCU based
> approach. Which does two basic steps:
>
> - Main thread wraps the setup phase in an SRCU read-side
> critical section. Pair of srcu_read_lock()/srcu_read_unlock().
> - Each worker calls synchronize_srcu() on entry, ensuring
> it waits for the initialization phase to be completed.
>
> This patch eliminates the need for down_read()/up_read() and
> down_write()/up_write() pairs thus simplifying the logic and improving clarity.
>
> Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
> ---
> lib/test_vmalloc.c | 17 +++++++----------
> 1 file changed, 7 insertions(+), 10 deletions(-)
Reviewed-by: Adrian Huang <ahuang12@lenovo.com>
Tested-by: Adrian Huang <ahuang12@lenovo.com>
> diff --git a/lib/test_vmalloc.c b/lib/test_vmalloc.c index
> f585949ff696e..4ab23e5e772d0 100644
> --- a/lib/test_vmalloc.c
> +++ b/lib/test_vmalloc.c
> @@ -13,9 +13,9 @@
> #include <linux/moduleparam.h>
> #include <linux/completion.h>
> #include <linux/delay.h>
> -#include <linux/rwsem.h>
> #include <linux/mm.h>
> #include <linux/rcupdate.h>
> +#include <linux/srcutree.h>
> #include <linux/slab.h>
>
> #define __param(type, name, init, msg) \
> @@ -58,10 +58,9 @@ __param(int, run_test_mask, INT_MAX, );
>
> /*
> - * Read write semaphore for synchronization of setup
> - * phase that is done in main thread and workers.
> + * This is for synchronization of setup phase.
> */
> -static DECLARE_RWSEM(prepare_for_test_rwsem);
> +DEFINE_STATIC_SRCU(prepare_for_test_srcu);
>
> /*
> * Completion tracking for worker threads.
> @@ -458,7 +457,7 @@ static int test_func(void *private)
> /*
> * Block until initialization is done.
> */
> - down_read(&prepare_for_test_rwsem);
> + synchronize_srcu(&prepare_for_test_srcu);
>
> t->start = get_cycles();
> for (i = 0; i < ARRAY_SIZE(test_case_array); i++) { @@ -487,8 +486,6 @@
> static int test_func(void *private)
> t->data[index].time = delta;
> }
> t->stop = get_cycles();
> -
> - up_read(&prepare_for_test_rwsem);
> test_report_one_done();
>
> /*
> @@ -526,7 +523,7 @@ init_test_configuration(void)
>
> static void do_concurrent_test(void)
> {
> - int i, ret;
> + int i, ret, idx;
>
> /*
> * Set some basic configurations plus sanity check.
> @@ -538,7 +535,7 @@ static void do_concurrent_test(void)
> /*
> * Put on hold all workers.
> */
> - down_write(&prepare_for_test_rwsem);
> + idx = srcu_read_lock(&prepare_for_test_srcu);
>
> for (i = 0; i < nr_threads; i++) {
> struct test_driver *t = &tdriver[i];
> @@ -555,7 +552,7 @@ static void do_concurrent_test(void)
> /*
> * Now let the workers do their job.
> */
> - up_write(&prepare_for_test_rwsem);
> + srcu_read_unlock(&prepare_for_test_srcu, idx);
>
> /*
> * Sleep quiet until all workers are done with 1 second
> --
> 2.39.5
>
prev parent reply other threads:[~2025-04-24 13:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 16:12 Uladzislau Rezki (Sony)
2025-04-17 16:12 ` [PATCH 2/4] lib/test_vmalloc.c: Allow built-in execution Uladzislau Rezki (Sony)
2025-04-18 15:01 ` Baoquan He
2025-04-24 13:37 ` Adrian Huang12
2025-06-13 13:59 ` Dev Jain
2025-06-13 14:19 ` Uladzislau Rezki
2025-06-13 14:23 ` Dev Jain
2025-06-13 14:37 ` Uladzislau Rezki
2025-06-14 10:27 ` Dev Jain
2025-06-14 15:35 ` Uladzislau Rezki
2025-04-17 16:12 ` [PATCH 3/4] MAINTAINERS: Add test_vmalloc.c to VMALLOC section Uladzislau Rezki (Sony)
2025-04-18 15:01 ` Baoquan He
2025-04-17 16:12 ` [PATCH 4/4] vmalloc: Align nr_vmalloc_pages and vmap_lazy_nr Uladzislau Rezki (Sony)
2025-04-18 13:26 ` Baoquan He
2025-04-24 13:38 ` Adrian Huang12
2025-04-18 18:12 ` [PATCH 1/4] lib/test_vmalloc.c: Replace RWSEM to SRCU for setup kernel test robot
2025-04-22 12:59 ` Uladzislau Rezki
2025-04-24 13:35 ` Adrian Huang12 [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=TYZPR03MB6192BA354C0B1DE09AF1D184B3852@TYZPR03MB6192.apcprd03.prod.outlook.com \
--to=ahuang12@lenovo.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oleksiy.avramchenko@sony.com \
--cc=urezki@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