From: Davidlohr Bueso <dave@stgolabs.net>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: linux-kernel@vger.kernel.org,
Josh Triplett <josh@joshtriplett.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
rcu@vger.kernel.org, connoro@google.com
Subject: Re: [PATCH v2 2/2] locktorture: Make the rt_boost factor a tunable
Date: Fri, 9 Dec 2022 14:32:32 -0800 [thread overview]
Message-ID: <20221209223232.2dqjeamad6nhlcmp@offworld> (raw)
In-Reply-To: <CAEXW_YRyhXvvyiw=TrPLk4UwBThqeUh+aP_pvCiBSr6Mko2zxg@mail.gmail.com>
On Fri, 09 Dec 2022, Joel Fernandes wrote:
>> >- * Boost priority once every ~50k operations. When the
>> >- * task tries to take the lock, the rtmutex it will account
>> >+ * Boost priority once every rt_boost_factor operations. When
>> >+ * the task tries to take the lock, the rtmutex it will account
>>
>> Nit: maybe refer to it as 'rt_boost_factor'?
>
>Sorry, I did not follow. Refer to what?
Just use single quotes to refer to the parameter.
Thanks,
Davidlohr
next prev parent reply other threads:[~2022-12-09 22:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 2:23 [PATCH v2 1/2] locktorture: Allow non-rtmutex lock types to be boosted Joel Fernandes (Google)
2022-12-09 2:23 ` [PATCH v2 2/2] locktorture: Make the rt_boost factor a tunable Joel Fernandes (Google)
2022-12-09 16:37 ` Davidlohr Bueso
2022-12-09 21:51 ` Joel Fernandes
2022-12-09 22:32 ` Davidlohr Bueso [this message]
2022-12-09 23:23 ` Joel Fernandes
2022-12-09 2:26 ` [PATCH v2 1/2] locktorture: Allow non-rtmutex lock types to be boosted Joel Fernandes
2022-12-09 3:25 ` Davidlohr Bueso
2022-12-09 3:58 ` Joel Fernandes
2022-12-09 16:34 ` Davidlohr Bueso
2022-12-09 17:02 ` Joel Fernandes
2022-12-13 20:24 ` Paul E. McKenney
2022-12-13 20:51 ` Joel Fernandes
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=20221209223232.2dqjeamad6nhlcmp@offworld \
--to=dave@stgolabs.net \
--cc=connoro@google.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.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
all inboxes | Powered by JetHome®