[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070429071117.GA3612@elte.hu>
Date: Sun, 29 Apr 2007 09:11:17 +0200
From: Ingo Molnar <mingo@...e.hu>
To: S.Çağlar Onur <caglar@...dus.org.tr>
Cc: linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Con Kolivas <kernel@...ivas.org>,
Nick Piggin <npiggin@...e.de>, Mike Galbraith <efault@....de>,
Arjan van de Ven <arjan@...radead.org>,
Peter Williams <pwil3058@...pond.net.au>,
Thomas Gleixner <tglx@...utronix.de>, Willy Tarreau <w@....eu>,
Gene Heskett <gene.heskett@...il.com>, Mark Lord <lkml@....ca>,
Zach Carter <linux@...hcarter.com>,
Kasper Sandberg <lkml@...anurb.dk>,
buddabrod <buddabrod@...il.com>,
Srivatsa Vaddagiri <vatsa@...ibm.com>
Subject: Re: [patch] CFS scheduler, -v7
* S.Çağlar Onur <caglar@...dus.org.tr> wrote:
> Ingo, please ignore my first report until i found a proper way to
> reproduce the slowness cause currently CFS-v7, CFS-v7 + "renice
> patch", CFS-v7 + renice + your private mail suggestions and CFS-v6 +
> "PI support for futexes patch" seems works equally (which is a good
> thing so X renicing seems really not needed, [...]
oh, good!
> [...] and there were no regression instead of my daydreams) or im too
> tired to understand the differences.
could the CPU have dropped speed for that bootup (some CPUs do that
automatically upon overheating), or perhaps if you are using some RAID
array, could it have done a background resync? Especially the bootup
slowdown you saw seemed significant, and because bootup speed is 90% IO
dominated, the CPU scheduler seems an unlikely candidate.
Ingo
-
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