[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1385188503.5296.17.camel@marge.simpson.net>
Date: Sat, 23 Nov 2013 07:35:03 +0100
From: Mike Galbraith <efault@....de>
To: Darren Hart <dvhart@...ux.intel.com>
Cc: Davidlohr Bueso <davidlohr@...com>, linux-kernel@...r.kernel.org,
mingo@...nel.org, peterz@...radead.org, tglx@...utronix.de,
jeffm@...e.com, torvalds@...ux-foundation.org, scott.norton@...com,
tom.vaden@...com, aswin@...com, Waiman.Long@...com,
jason.low2@...com
Subject: Re: [PATCH 0/5] futex: Wakeup optimizations
On Fri, 2013-11-22 at 21:55 -0800, Darren Hart wrote:
> On Fri, 2013-11-22 at 16:56 -0800, Davidlohr Bueso wrote:
> > This patchset has also been tested on smaller systems for a variety of
> > benchmarks, including java workloads, kernel builds and custom bang-the-hell-out-of
> > hb locks programs. So far, no functional or performance regressions have been seen.
> > Furthermore, no issues were found when running the different tests in the futextest
> > suite: http://git.kernel.org/cgit/linux/kernel/git/dvhart/futextest.git/
>
> Excellent. Would you be able to contribute any of these (C only please)
> to the stress test group?
FWIW, I plugged this series into an rt kernel (extra raciness) and beat
it up a bit on a 64 core box too. Nothing fell out, nor did futextest
numbers change outside variance (poor box has 8 whole gig ram, single
numa node, so kinda crippled/wimpy, and not good box for benchmarking).
What concerned me most about the series was 5/5.. looks like a great
idea to me, but the original thread did not have a happy ending.
-Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists