On Wed, May 07, 2014 at 02:20:15PM -0700, j...@joshtriplett.org wrote:
> On Mon, Apr 28, 2014 at 05:24:54PM -0700, Paul E. McKenney wrote:
> > From: "Paul E. McKenney"
> >
> > The current lock_torture_writer() spends too much time sleeping and not
> > enough time hammering locks, as in an
On Mon, Apr 28, 2014 at 05:24:54PM -0700, Paul E. McKenney wrote:
> From: "Paul E. McKenney"
>
> The current lock_torture_writer() spends too much time sleeping and not
> enough time hammering locks, as in an eight-CPU test will often only be
> utilizing a CPU or two. This commit therefore
On Mon, Apr 28, 2014 at 05:24:54PM -0700, Paul E. McKenney wrote:
From: Paul E. McKenney paul...@linux.vnet.ibm.com
The current lock_torture_writer() spends too much time sleeping and not
enough time hammering locks, as in an eight-CPU test will often only be
utilizing a CPU or two. This
On Wed, May 07, 2014 at 02:20:15PM -0700, j...@joshtriplett.org wrote:
On Mon, Apr 28, 2014 at 05:24:54PM -0700, Paul E. McKenney wrote:
From: Paul E. McKenney paul...@linux.vnet.ibm.com
The current lock_torture_writer() spends too much time sleeping and not
enough time hammering locks,
From: "Paul E. McKenney"
The current lock_torture_writer() spends too much time sleeping and not
enough time hammering locks, as in an eight-CPU test will often only be
utilizing a CPU or two. This commit therefore makes lock_torture_writer()
sleep less and hammer more.
Signed-off-by: Paul E.
From: Paul E. McKenney paul...@linux.vnet.ibm.com
The current lock_torture_writer() spends too much time sleeping and not
enough time hammering locks, as in an eight-CPU test will often only be
utilizing a CPU or two. This commit therefore makes lock_torture_writer()
sleep less and hammer more.
6 matches
Mail list logo