[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f3c4b15956d12314d626906c190f6164.squirrel@webmail-b.css.fujitsu.com>
Date: Thu, 26 Feb 2009 19:55:31 +0900 (JST)
From: "KAMEZAWA Hiroyuki" <kamezawa.hiroyu@...fujitsu.com>
To: "Peter Zijlstra" <a.p.zijlstra@...llo.nl>
Cc: "KAMEZAWA Hiroyuki" <kamezawa.hiroyu@...fujitsu.com>,
"Bharata B Rao" <bharata.rao@...il.com>,
"Li Zefan" <lizf@...fujitsu.com>, "Ingo Molnar" <mingo@...e.hu>,
"Paul Menage" <menage@...gle.com>,
"Balbir Singh" <balbir@...ux.vnet.ibm.com>,
"LKML" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] cpuacct: add a branch prediction
Peter Zijlstra wrote:
> On Thu, 2009-02-26 at 19:28 +0900, KAMEZAWA Hiroyuki wrote:
>
>> Taking hierarchy mutex while reading will make read-side stable.
>
> We're talking about scheduling here, taking a mutex to stop scheduling
> won't work, nor will it be acceptible to use anything that will.
>
I'm sorry but I thought we are talking about cpuacct subsystem and not
cpu subsystem....cpuacct subsystem's information is used for schedule ?
Is there a user of information gathered by cpuacct subsystem in the kernel ?
I thought only user(reader) is the user who read cpuacct.usage file.
Thanks,
-Kame
--
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