On Thu, 2013-08-08 at 00:08 -0400, Steven Rostedt wrote:
> I went to do some benchmarks on the jump label code, and ran:
>
>
> perf stat -r 100 ./hackbench 50
>
Note, perf doesn't even need to be involved. Running hackbench manually
three times causes the bug too.
-- Steve
--
To unsubscribe
On Thu, 2013-08-08 at 14:04 +0900, Joonsoo Kim wrote:
> Sorry about it.
> Now, I think that this is a buggy commit, so should be reverted.
>
> For confirm that, could I ask a question about your configuration, Steven?
> I guess, you may set 0 to all kmem caches's cpu_partial via sysfs, doesn't it
On Thu, Aug 08, 2013 at 12:08:56AM -0400, Steven Rostedt wrote:
> I went to do some benchmarks on the jump label code, and ran:
>
>
> perf stat -r 100 ./hackbench 50
>
> It ran twice, and then would die with:
>
> [ 65.785108] hackbench invoked oom-killer: gfp_mask=0x200da, order=0,
> oom_sco
I went to do some benchmarks on the jump label code, and ran:
perf stat -r 100 ./hackbench 50
It ran twice, and then would die with:
[ 65.785108] hackbench invoked oom-killer: gfp_mask=0x200da, order=0,
oom_score_adj=0
[ 65.792921] hackbench cpuset=/ mems_allowed=0
[ 65.797286] CPU: 6 PI
4 matches
Mail list logo