linux-kernel - Re: [PATCH v2 2/2] locktorture: Make the rt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20221209223232.2dqjeamad6nhlcmp@offworld>
Date:   Fri, 9 Dec 2022 14:32:32 -0800
From:   Davidlohr Bueso <dave@...olabs.net>
To:     Joel Fernandes <joel@...lfernandes.org>
Cc:     linux-kernel@...r.kernel.org,
        Josh Triplett <josh@...htriplett.org>,
        "Paul E. McKenney" <paulmck@...nel.org>, rcu@...r.kernel.org,
        connoro@...gle.com
Subject: Re: [PATCH v2 2/2] locktorture: Make the rt_boost factor a tunable

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