[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6599ad830802290208l6b9d97d1l67e351fc2f9112f7@mail.gmail.com>
Date: Fri, 29 Feb 2008 02:08:45 -0800
From: "Paul Menage" <menage@...gle.com>
To: "Dhaval Giani" <dhaval@...ux.vnet.ibm.com>
Cc: vatsa@...ux.vnet.ibm.com, balbir@...ux.vnet.ibm.com, mingo@...e.hu,
linux-kernel@...r.kernel.org, a.p.zijlstra@...llo.nl,
akpm@...ux-foundation.org, skumar@...ux.vnet.ibm.com
Subject: Re: [patch 2/2] sched: allow cpuacct stats to be reset
On Thu, Feb 28, 2008 at 10:04 PM, Dhaval Giani
<dhaval@...ux.vnet.ibm.com> wrote:
> On Thu, Feb 28, 2008 at 09:48:51PM -0800, Paul Menage wrote:
>
> > On Thu, Feb 28, 2008 at 8:32 PM, Dhaval Giani <dhaval@...ux.vnet.ibm.com> wrote:
> >
>
> > Can I suggest, in order to be more generic, that this patch instead
> > set each CPU's counter to the written value divided by the number of
> > CPUs? (Either forgetting the remainder, or spreading it among the
> > first few CPUs).
> >
>
> This patch is only allowing a reset of the stats. In what sort of a
> situation would one be looking for changing the usage value?
How about Checkpoint/Restart?
It seems that if you're going to the effort to notice a non-zero value
and return an error, it wouldn't be much more effort to do something
useful with that non-zero value instead.
Paul
--
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