[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1322558612.2921.182.camel@twins>
Date: Tue, 29 Nov 2011 10:23:32 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Satoru Moriya <satoru.moriya@....com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"bsingharora@...il.com" <bsingharora@...il.com>,
"mingo@...e.hu" <mingo@...e.hu>,
"nagar@...son.ibm.com" <nagar@...son.ibm.com>,
"kobayashi.kk@...s.nec.co.jp" <kobayashi.kk@...s.nec.co.jp>,
Randy Dunlap <rdunlap@...otime.net>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"dle-develop@...ts.sourceforge.net"
<dle-develop@...ts.sourceforge.net>,
Seiji Aguchi <seiji.aguchi@....com>
Subject: Re: [PATCH 0/4] delayacct: save max CPU/IO/SWAP/RECLAIM delays
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.
--
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