On Wed, 2015-07-22 at 17:17 -0700, Paul E. McKenney wrote:
> On Wed, Jul 22, 2015 at 02:07:27PM -0700, Davidlohr Bueso wrote:
> > Real time mutexes is one of the few general primitives
> > that we do not have in locktorture. Address this -- a few
> > considerations:
> >
> > o To spice things up,
On Wed, 2015-07-22 at 17:17 -0700, Paul E. McKenney wrote:
On Wed, Jul 22, 2015 at 02:07:27PM -0700, Davidlohr Bueso wrote:
Real time mutexes is one of the few general primitives
that we do not have in locktorture. Address this -- a few
considerations:
o To spice things up, enable
On Wed, Jul 22, 2015 at 02:07:27PM -0700, Davidlohr Bueso wrote:
> Real time mutexes is one of the few general primitives
> that we do not have in locktorture. Address this -- a few
> considerations:
>
> o To spice things up, enable competing thread(s) to become
> rt, such that we can stress
Real time mutexes is one of the few general primitives
that we do not have in locktorture. Address this -- a few
considerations:
o To spice things up, enable competing thread(s) to become
rt, such that we can stress different prio boosting paths
in the rtmutex code. Introduce a ->task_boost
Real time mutexes is one of the few general primitives
that we do not have in locktorture. Address this -- a few
considerations:
o To spice things up, enable competing thread(s) to become
rt, such that we can stress different prio boosting paths
in the rtmutex code. Introduce a -task_boost
On Wed, Jul 22, 2015 at 02:07:27PM -0700, Davidlohr Bueso wrote:
Real time mutexes is one of the few general primitives
that we do not have in locktorture. Address this -- a few
considerations:
o To spice things up, enable competing thread(s) to become
rt, such that we can stress different
6 matches
Mail list logo
