On Fri, 17 Aug 2007, Mathieu Desnoyers wrote:
> > The cpu will definitely not be idle during these measurements and no
> > frequency scaling is active.
>
> The problem is that if the cpu is idle _before_ the measurements, the
> frequency will change differently from one cpu to another. Therefore
* Christoph Lameter ([EMAIL PROTECTED]) wrote:
> On Fri, 17 Aug 2007, Mathieu Desnoyers wrote:
>
> > Why do you printk inside the timing period ? Filling the printk buffers
> > or outputting on things such as serial console could really hurt your
> > results.
>
> It was easier to code?
>
> > I h
On Fri, 17 Aug 2007, Mathieu Desnoyers wrote:
> Why do you printk inside the timing period ? Filling the printk buffers
> or outputting on things such as serial console could really hurt your
> results.
It was easier to code?
> I hope you run your system with idle=poll and without frequency scal
Hi Christoph,
A few remarks on these tests:
Why do you printk inside the timing period ? Filling the printk buffers
or outputting on things such as serial console could really hurt your
results.
I hope you run your system with idle=poll and without frequency scaling
at all, because otherwise you
With this patch SLUB will perform tests on bootup and display results.
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
---
mm/slub.c | 97 +---
1 files changed, 92 insertions(+), 5 deletions(-)
diff --git a/mm/slub.c b/mm/slub.c
inde
5 matches
Mail list logo
