The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Satoru Moriya <satoru.moriya@hds.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"bsingharora@gmail.com" <bsingharora@gmail.com>,
	"mingo@elte.hu" <mingo@elte.hu>,
	"nagar@watson.ibm.com" <nagar@watson.ibm.com>,
	"kobayashi.kk@ncos.nec.co.jp" <kobayashi.kk@ncos.nec.co.jp>,
	Randy Dunlap <rdunlap@xenotime.net>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"dle-develop@lists.sourceforge.net" 
	<dle-develop@lists.sourceforge.net>,
	Seiji Aguchi <seiji.aguchi@hds.com>
Subject: Re: [PATCH 0/4] delayacct: save max CPU/IO/SWAP/RECLAIM delays
Date: Tue, 29 Nov 2011 10:23:32 +0100	[thread overview]
Message-ID: <1322558612.2921.182.camel@twins> (raw)
In-Reply-To: <65795E11DBF1E645A09CEC7EAEE94B9CB574E70D@USINDEVS02.corp.hds.com>

On Mon, 2011-11-28 at 17:44 -0500, Satoru Moriya wrote:
> In the latency sensitive systems, we usually focus on the worst latency.
> And so, it is useful to save max delays into the per-task delay
> accounting functionality.
> 
> Example output:
> (on 100 concurrent dd reading sparse files w/ 1 dd writing a file)
> 
> CPU             count     real total  virtual total    delay total      delay_max  delay average
>                   222       45993008       74603882        7637295        3691858          0.034ms
> IO              count    delay total      delay max  delay average
>                     2       21812073       12728672             10ms
> SWAP            count    delay total      delay max  delay average
>                     0              0              0              0ms
> RECLAIM         count    delay total      delay_max  delay average
>                     2         348488         211985              0ms
> 
> Any comments are welcome.

No!!!

Linus told us to be bastards, so there you have it.

There's way too many different accounting crap thingies around. And now
I get a patch without any justification what so ever. So no, piss off.

  parent reply	other threads:[~2011-11-29  9:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28 22:44 [PATCH 0/4] delayacct: save max CPU/IO/SWAP/RECLAIM delays Satoru Moriya
2011-11-28 22:44 ` [PATCH 1/4] sched: add members to struct sched_info to save maximum Satoru Moriya
2011-11-28 22:45 ` [PATCH 2/4] delayacct: add members to struct task_delay_info to save max delays Satoru Moriya
2011-11-28 22:46 ` [PATCH 3/4] delayacct: update taskstats " Satoru Moriya
2011-11-28 22:47 ` [PATCH 4/4] getdelays: show max CPU/IO/SWAP/RECLAIM delays Satoru Moriya
2011-11-29  9:23 ` Peter Zijlstra [this message]
2011-11-29 22:34   ` [PATCH 0/4] delayacct: save " Satoru Moriya

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=1322558612.2921.182.camel@twins \
    --to=peterz@infradead.org \
    --cc=bsingharora@gmail.com \
    --cc=dle-develop@lists.sourceforge.net \
    --cc=kobayashi.kk@ncos.nec.co.jp \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nagar@watson.ibm.com \
    --cc=rdunlap@xenotime.net \
    --cc=satoru.moriya@hds.com \
    --cc=seiji.aguchi@hds.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