[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87d472gyw9.fsf@basil.nowhere.org>
Date: Tue, 11 Aug 2009 17:20:54 +0200
From: Andi Kleen <andi@...stfloor.org>
To: Prarit Bhargava <prarit@...hat.com>
Cc: balbir@...ux.vnet.ibm.com,
Andrew Morton <akpm@...ux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
"nishimura@....nes.nec.co.jp" <nishimura@....nes.nec.co.jp>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
"menage@...gle.com" <menage@...gle.com>, andi.kleen@...el.com,
Pavel Emelianov <xemul@...nvz.org>,
"lizf@...fujitsu.com" <lizf@...fujitsu.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: Help Resource Counters Scale better (v4)
Prarit Bhargava <prarit@...hat.com> writes:
>
> On a 64p/32G system running 2.6.31-git2-rc5, with RESOURCE_COUNTERS
This is CONFIG_RESOURCE_COUNTERS off at compile time right?
> off, "time make -j64" results in
>
> real 4m54.972s
> user 90m13.456s
> sys 50m19.711s
>
> On the same system, running 2.6.31-git2-rc5, with RESOURCE_COUNTERS on,
> plus Balbir's "Help Resource Counters Scale Better (v3)" patch, and
> this patch, results in
>
> real 4m18.607s
> user 84m58.943s
> sys 50m52.682s
Hmm, so resource counters on with the patch is faster than
CONFIG_RESOURCE_COUNTERS compiled out in real time? That seems
counterintuitive. At best I would expect the patch to break even, but
not be actually faster.
Is the compilation stable over multiple runs?
Still it looks like the patch is clearly needed.
-Andi
--
ak@...ux.intel.com -- Speaking for myself only.
--
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