From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Dario Faggioli <raistlin@linux.it>
Cc: Dhaval Giani <dhaval.giani@gmail.com>, 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>,
vatsa@in.ibm.com
Subject: Re: Sending some form of notifaction when sched_fifo throttling kicks in...
Date: Sun, 26 Dec 2010 00:35:04 +0530 [thread overview]
Message-ID: <20101225190504.GB3393@balbir.in.ibm.com> (raw)
In-Reply-To: <1293115496.3390.49.camel@Palantir>
* Dario Faggioli <raistlin@linux.it> [2010-12-23 15:44:56]:
> On Thu, 2010-12-23 at 15:04 +0100, Dhaval Giani wrote:
> > > ... If you think you're fine with some /proc (and perhaps cpuacct, if
> > > cgroups are being used) readable, I can try to come up with something.
> > >
> >
> > There is no point in putting it in cpuacct since cpuacct can be used
> > separately from cpu.
> >
> Which would mean that you'd need both for having such stat. Anyway, I'm
> fine with putting this in 'cpu' as well, just trying to find a consensus
> on what the right place is.
>
> > > Do others have some idea and/or comments about that? This is
> > > ABI/interface, and that really scares me! :-P
> >
> > IIRC, your patchset had something like this for getting the
> > statistics? Starting fromt hre, would schedstats be the right place?
> >
> SCHED_DEADLINE patchset has both signaling capabilities and some
> statistic reporting, bat it's a different thing.
>
> I think schedstat could be the right place for _this_ thing here, but
> since each cgroup could be throttled, we also need something which is
> per-cgroup... Don't you agree?
>
You definitely need something per cgroup, have you looked at the
events framework in cgroups and its implementation in memcgroup?
--
Three Cheers,
Balbir
next prev parent reply other threads:[~2010-12-25 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 11:39 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 [this message]
2010-12-27 6:43 ` Bharata B Rao
2010-12-28 10:30 ` Dario Faggioli
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=20101225190504.GB3393@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.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=raistlin@linux.it \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torbenh@gmx.de \
--cc=vatsa@in.ibm.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®