Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20221209022305.321149-1-joel@joelfernandes.org>
 <20221209022305.321149-2-joel@joelfernandes.org> <20221209163759.6s7pqf5wdvy32ywn@offworld>
 <CAEXW_YRyhXvvyiw=TrPLk4UwBThqeUh+aP_pvCiBSr6Mko2zxg@mail.gmail.com> <20221209223232.2dqjeamad6nhlcmp@offworld>
In-Reply-To: <20221209223232.2dqjeamad6nhlcmp@offworld>
From:   Joel Fernandes <joel@joelfernandes.org>
Date:   Fri, 9 Dec 2022 23:23:19 +0000
Message-ID: <CAEXW_YTLuRU2fxnijoez8m8n50L-FcU46cOLUPgp15m0C8fdxg@mail.gmail.com>
Subject: Re: [PATCH v2 2/2] locktorture: Make the rt_boost factor a tunable
To:     Davidlohr Bueso <dave@stgolabs.net>
Cc:     linux-kernel@vger.kernel.org,
        Josh Triplett <josh@joshtriplett.org>,
        "Paul E. McKenney" <paulmck@kernel.org>, rcu@vger.kernel.org,
        connoro@google.com
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Fri, Dec 9, 2022 at 10:56 PM Davidlohr Bueso <dave@stgolabs.net> wrote:
>
> 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.

Ah, got it. Will do (either next respin or Paul can do it) and thank you.


 - Joel