From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: nicolas.pitre@linaro.org, shreyas@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, peterz@infradead.org,
rafael@kernel.org, vincent.guittot@linaro.org
Subject: Re: [PATCH V7] irq: Track the interrupt timings
Date: Thu, 23 Jun 2016 15:12:25 +0200 [thread overview]
Message-ID: <576BE039.9060703@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.11.1606231153100.5839@nanos>
On 06/23/2016 12:12 PM, Thomas Gleixner wrote:
> On Thu, 23 Jun 2016, Daniel Lezcano wrote:
>> On 06/23/2016 10:41 AM, Thomas Gleixner wrote:
>>> Is it really required to do this per interrupt rather than providing per cpu
>>> statistics of interrupts which arrived in the last X seconds or whatever
>>> timeframe is relevant for this.
>>
>> Perhaps I am misunderstanding but if the statistics are done per cpu without
>> tracking per irq timings, it is not possible to extract a repeating pattern
>> for each irq and have an accurate prediction.
>
> I don't see why you need a repeating pattern for each irq. All you want to
> know is whether there are repeating patterns of interrupts on a particular
> cpu.
>
> struct per_cpu_stat {
> u32 irq;
> u64 ts;
> };
>
> storing 32 entries of the above should give you enough information about
> patterns etc. If you have a high rate of interrupts on that cpu it does not
> matter at all whether thats from one or several devices. If you have only a
> few then this storage is sufficient to get the desired information.
Mmmh, yes. I will investigate this patchset by replacing the percpu
irqdesc's timings field by a per cpu irq event timings array.
Thanks !
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
prev parent reply other threads:[~2016-06-23 13:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 16:33 [PATCH V5] irq: Track the interrupt timings Daniel Lezcano
2016-06-14 17:46 ` Nicolas Pitre
2016-06-14 18:11 ` Thomas Gleixner
2016-06-14 19:52 ` Daniel Lezcano
2016-06-14 20:10 ` [PATCH V6] " Daniel Lezcano
2016-06-14 20:38 ` Nicolas Pitre
2016-06-17 13:46 ` Thomas Gleixner
2016-06-17 17:16 ` [PATCH V7] " Daniel Lezcano
2016-06-23 8:41 ` Thomas Gleixner
2016-06-23 9:39 ` Daniel Lezcano
2016-06-23 10:12 ` Thomas Gleixner
2016-06-23 13:12 ` Daniel Lezcano [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=576BE039.9060703@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=shreyas@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
/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