mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joel Fernandes <joel@joelfernandes.org>
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
Subject: Re: [PATCH v2 1/2] locktorture: Allow non-rtmutex lock types to be boosted
Date: Thu, 8 Dec 2022 22:58:36 -0500	[thread overview]
Message-ID: <2D7B1E52-D2FC-45ED-A739-BA9A1213FD49@joelfernandes.org> (raw)
In-Reply-To: <20221209032550.p4tcyypgkuspp2ur@offworld>



> On Dec 8, 2022, at 10:50 PM, Davidlohr Bueso <dave@stgolabs.net> wrote:
> 
> On Fri, 09 Dec 2022, Joel Fernandes (Google) wrote:
> 
>> Currently RT boosting is only done for rtmutex_lock, however with proxy
>> execution, we also have the mutex_lock participating in priorities. To
>> exercise the testing better, add RT boosting to other lock testing types
>> as well, using a new knob (rt_boost).
> 
> No particular objection to the patches, but shouldn't these go as part
> of the next iteration of the PE series?

Hey Davidlohr,
Nice to hear from you. Paul was interested in these for some things he is looking at and also as general clean up ;)

Thanks.



> 
> Thanks,
> Davidlohr

  reply	other threads:[~2022-12-09  3:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09  2:23 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
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 [this message]
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=2D7B1E52-D2FC-45ED-A739-BA9A1213FD49@joelfernandes.org \
    --to=joel@joelfernandes.org \
    --cc=connoro@google.com \
    --cc=dave@stgolabs.net \
    --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®