Re: 2.5.50 + e100 benchmarking

Anton Blanchard
2002-12-09T13:53:54Z

> That has to be a CPU scheduler problem; I think Andrea identified
> a glitch which could do that.
>
> Could you put together an isolated testcase?

It might have been operator error, still trying to reproduce it.

Anton