[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=1v6YG-Vc7uZFvqO6K0fAuZ-o9A7hxeZVVAHm3@mail.gmail.com>
Date: Thu, 23 Dec 2010 15:04:14 +0100
From: Dhaval Giani <dhaval.giani@...il.com>
To: Dario Faggioli <raistlin@...ux.it>
Cc: torbenh <torbenh@....de>, linux-kernel@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>,
Gregory Haskins <ghaskins@...ell.com>,
Nick Piggin <nickpiggin@...oo.com.au>,
Balbir Singh <balbir@...ux.vnet.ibm.com>, vatsa@...ibm.com
Subject: Re: Sending some form of notifaction when sched_fifo throttling kicks in...
?
>>
> ... 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.
> I think that the number of times that throttling fired and the last
> throttling instant could be exported this way without much issues.
>
> 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?
Dhaval
--
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