From: Dario Faggioli <raistlin@linux.it>
To: Bharata B Rao <bharata.rao@gmail.com>
Cc: torbenh <torbenh@gmx.de>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Gregory Haskins <ghaskins@novell.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Dhaval Giani <dhaval.giani@gmail.com>
Subject: Re: Sending some form of notifaction when sched_fifo throttling kicks in...
Date: Tue, 28 Dec 2010 11:30:10 +0100 [thread overview]
Message-ID: <1293532210.2899.1002.camel@Palantir> (raw)
In-Reply-To: <AANLkTinch3-FHaOKTnfYnFLnG5uyRNfmpZP=RpLzJOrf@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
On Mon, 2010-12-27 at 12:13 +0530, Bharata B Rao wrote:
> > Do others have some idea and/or comments about that? This is
> > ABI/interface, and that really scares me! :-P
>
> You might want to note that CFS bandwidth control patches export some
> such stats via a new per-cgroup file cpu.stat. It exports 3 statistics:
>
Yeah, I saw that. What can be also done is to extend schedstats and then
apply it to cgroups as well... I think Dhaval told me he has some plans
about that, am I wrong?
> nr_periods: Number of enforcement intervals that have elapsed.
> nr_throttled: Number of times the group has been throttled/limited.
> throttled_time: The total time duration (in nanoseconds) for which the group
> remained throttled.
>
More than reasonable reporting, to me at least. :-)
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
----------------------------------------------------------------------
Dario Faggioli, ReTiS Lab, Scuola Superiore Sant'Anna, Pisa (Italy)
http://retis.sssup.it/people/faggioli -- dario.faggioli@jabber.org
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-12-28 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 11:39 Sending some form of notifaction when sched_fifo throttling kicks in torbenh
2010-12-23 13:17 ` Dario Faggioli
2010-12-23 14:04 ` Dhaval Giani
2010-12-23 14:44 ` Dario Faggioli
2010-12-25 19:05 ` Balbir Singh
2010-12-27 6:43 ` Bharata B Rao
2010-12-28 10:30 ` Dario Faggioli [this message]
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=1293532210.2899.1002.camel@Palantir \
--to=raistlin@linux.it \
--cc=bharata.rao@gmail.com \
--cc=dhaval.giani@gmail.com \
--cc=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torbenh@gmx.de \
/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