From: Joel Fernandes <joelagnelf@nvidia.com>
To: Uladzislau Rezki <urezki@gmail.com>
Cc: "Paul E . McKenney" <paulmck@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>, RCU <rcu@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Cheung Wall <zzqq0103.hey@gmail.com>,
Neeraj upadhyay <Neeraj.Upadhyay@amd.com>,
Joel Fernandes <joel@joelfernandes.org>,
Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>
Subject: Re: [PATCH v3 1/3] rcutorture: Allow a negative value for nfakewriters
Date: Wed, 26 Feb 2025 12:49:41 -0500 [thread overview]
Message-ID: <a26d4cc5-ff54-4f9f-b2df-aa423c112487@nvidia.com> (raw)
In-Reply-To: <Z78lNRKjLQKigyLw@pc636>
On 2/26/2025 9:29 AM, Uladzislau Rezki wrote:
> On Tue, Feb 25, 2025 at 04:24:09PM -0500, Joel Fernandes wrote:
>> On Tue, Feb 25, 2025 at 12:00:18PM +0100, Uladzislau Rezki (Sony) wrote:
>>> Currently "nfakewriters" parameter can be set to any value but
>>> there is no possibility to adjust it automatically based on how
>>> many CPUs a system has where a test is run on.
>>>
>>> To address this, if the "nfakewriters" is set to negative it will
>>> be adjusted to num_online_cpus() during torture initialization.
>>>
>>> Reviewed-by: Paul E. McKenney <paulmck@kernel.org>
>>> Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
>>> ---
>>> kernel/rcu/rcutorture.c | 22 ++++++++++++++++------
>>> 1 file changed, 16 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/kernel/rcu/rcutorture.c b/kernel/rcu/rcutorture.c
>>> index d98b3bd6d91f..f376262532ce 100644
>>> --- a/kernel/rcu/rcutorture.c
>>> +++ b/kernel/rcu/rcutorture.c
>>> @@ -148,6 +148,7 @@ MODULE_PARM_DESC(torture_type, "Type of RCU to torture (rcu, srcu, ...)");
>>
>> IMO, this should also be updated to reflect the possibily to set it negative
>> and hence to number CPUs:
>>
>> torture_param(int, nfakewriters, 4, "Number of RCU fake writer threads");
>>
> You can set it to a negative as well as to number of CPUs or any other
> number.
Sorry I just meant amend the description to something like "Number of RCU fake
writer threads (or set to -1 for NR_CPUs)", so user does not have to read code
to know that (and update the kernel cmdline params document as well).
thanks,
- Joel
next prev parent reply other threads:[~2025-02-26 17:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 11:00 [PATCH v3 1/3] rcutorture: Allow a negative value for nfakewriters Uladzislau Rezki (Sony)
2025-02-25 11:00 ` [PATCH v3 2/3] rcu: Update TREE05.boot to test normal synchronize_rcu() Uladzislau Rezki (Sony)
2025-02-25 11:00 ` [PATCH v3 3/3] rcu: Use _full() API to debug synchronize_rcu() Uladzislau Rezki (Sony)
2025-02-25 15:48 ` Paul E. McKenney
2025-02-25 16:30 ` Uladzislau Rezki
2025-02-26 18:57 ` Boqun Feng
2025-02-26 20:48 ` Uladzislau Rezki
2025-02-26 21:12 ` Boqun Feng
2025-02-25 21:24 ` [PATCH v3 1/3] rcutorture: Allow a negative value for nfakewriters Joel Fernandes
2025-02-26 14:29 ` Uladzislau Rezki
2025-02-26 14:50 ` Paul E. McKenney
2025-02-26 15:40 ` Uladzislau Rezki
2025-02-26 17:49 ` Joel Fernandes [this message]
2025-02-26 18:04 ` Paul E. McKenney
2025-02-26 18:16 ` Uladzislau Rezki
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=a26d4cc5-ff54-4f9f-b2df-aa423c112487@nvidia.com \
--to=joelagnelf@nvidia.com \
--cc=Neeraj.Upadhyay@amd.com \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksiy.avramchenko@sony.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=urezki@gmail.com \
--cc=zzqq0103.hey@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