mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: balbir@linux.vnet.ibm.com
Cc: kosaki.motohiro@jp.fujitsu.com,
	LKML <linux-kernel@vger.kernel.org>,
	Bharata B Rao <bharata@linux.vnet.ibm.com>,
	Balaji Rao <balajirrao@gmail.com>,
	Dhaval Giani <dhaval@linux.vnet.ibm.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Ingo Molnar <mingo@elte.hu>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	seto.hidetoshi@jp.fujitsu.com
Subject: Re: [PATCH] cpuacct: VIRT_CPU_ACCOUNTING don't prevent percpu cputime count
Date: Wed, 29 Apr 2009 15:08:34 +0900 (JST)	[thread overview]
Message-ID: <20090429150116.4B1A.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20090429054453.GA789@balbir.in.ibm.com>

> > > This will make the end result very off the real value due to large
> > > batch value per cpu. If we are going to go this route, we should
> > > probably consider using __percpu_counter_sum so that the batch value
> > > does not show data that is way off.
> > 
> > No problem.
> > 
> > end-user don't see cputime itself. they see converted time.
> > cpuacct_stats_show() use cputime64_to_clock_t. it mean
> > the value less than 10msec don't display.
> >
> 
> Yes, I know, I reviewed Bharata's patch and suggested converting to
> clock_t for consistency with other metrics.

Oh, sorry.
I didn't know this.


> > --------------------------------------------------------
> > static int cpuacct_stats_show(struct cgroup *cgrp, struct cftype *cft,
> >                 struct cgroup_map_cb *cb)
> > {
> >         struct cpuacct *ca = cgroup_ca(cgrp);
> >         int i;
> > 
> >         for (i = 0; i < CPUACCT_STAT_NSTATS; i++) {
> >                 s64 val = percpu_counter_read(&ca->cpustat[i]);
> 
> My point is, this should probably be percpu_counter_sum(), but that
> can be expensive and we were willing to tollerate some inaccuracy due
> to batch value, I think your patch adds to the inaccuracy even more,
> even though it fixes a genuine problem.

Not expensive.
cpuacct_stats_show() is only called when reading stat file.
it definitely slow-path.
I think we can use percpu_counter_sum().

However, I doubt its worth.

before my patch:
  VIRT_CPU_ACCOUNTING=y:  accuracy but slow
  VIRT_CPU_ACCOUNTING=n:  inaccuracy few tick but fast

my patch
  VIRT_CPU_ACCOUNTING=y:  inaccuracy few tick but fast
  VIRT_CPU_ACCOUNTING=n:  inaccuracy few tick but fast

if my inaccuracy is wrong, current code is also crap when VIRT_CPU_ACCOUNTING=n.
I only make const accuracy to VIRT_CPU_ACCOUNTING=y and n.

Thought?
Although you still think percpu_counter_sum() is better, I can do it.


> 
> 
> >                 val = cputime64_to_clock_t(val);
> >                 cb->fill(cb, cpuacct_stat_desc[i], val);
> >         }
> >         return 0;
> > }
> > --------------------------------------------------------



  reply	other threads:[~2009-04-29  6:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28  6:53 KOSAKI Motohiro
2009-04-28  7:31 ` Bharata B Rao
2009-04-28  7:38   ` KOSAKI Motohiro
2009-04-28  7:50     ` Bharata B Rao
2009-04-28  8:10       ` KOSAKI Motohiro
2009-04-28 10:37         ` Bharata B Rao
2009-04-29  2:31           ` KOSAKI Motohiro
2009-04-29  3:30             ` Bharata B Rao
2009-04-28 22:08 ` Balbir Singh
2009-04-29  2:26   ` KOSAKI Motohiro
2009-04-29  5:44     ` Balbir Singh
2009-04-29  6:08       ` KOSAKI Motohiro [this message]
2009-04-29  3:21   ` Bharata B Rao
2009-04-29  6:04     ` Balbir Singh
2009-04-29  6:09       ` Bharata B Rao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090429150116.4B1A.A69D9226@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=balajirrao@gmail.com \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=dhaval@linux.vnet.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=schwidefsky@de.ibm.com \
    --cc=seto.hidetoshi@jp.fujitsu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®