Re: [LAD] itop

Oups, wrong link, bloody html... Let me try again:

https://gitorious.org/elboulangero/irqtop

On 04/21/2014 06:05 PM, elboulangero wrote:
> Hi,
>
> I'm just resurrecting this thread to inform that I renamed the tool to
> irqtop as suggested.
>
> New name, new link:
> https://gitorious.org/elboulangero/irqtop
> <https://gitorious.org/elboulangero/itop>
>
> I also added a man page, and fixed some little bugs here and there.
>
> Cheers
>
> On 05/26/2013 07:59 PM, Diego Veralli wrote:
>> Hey elboulangero,
>>
>> You might want to change the name, there are already 2 itops that I
>> know of, that monitor interrupts:
>>
>> * http://packages.debian.org/wheezy/itop
>> * http://et.redhat.com/~jmh/tools/xen/itop
>> <http://et.redhat.com/%7Ejmh/tools/xen/itop> (this is just a small
>> perl script, but still...)
>>
>> Yours provides much more information (works fine on my machine BTW),
>> so it's a useful addition, but if you just call it itop it's going to
>> be a bit confusing..
>>
>> Cheers
>> Diego
>>
>> On Fri, May 10, 2013 at 12:15 AM, elboulangero
>> <elboulangero@email-addr-hidden <mailto:elboulangero@email-addr-hidden>> wrote:
>>
>> Hello everyone,
>>
>> lately I had to fight big XRUN troubles, and thanks to this forum
>> I finally solved that. This excellent thread saved me:
>> http://linuxaudio.org/mailarchive/lau/2012/9/5/192706
>>
>> On my long quest, I tried to see a little bit more what happened
>> with the IRQs on my system. I searched for a kind of 'top'
>> utility to monitor the interrupts, but the only apps I found were
>> either deprecated, or missed some cool features.
>>
>> So, I ended up writing my own tool to monitor the file
>> /proc/interrupts.
>> It's available a this address:
>> https://gitorious.org/elboulangero/itop
>>
>> As its name indicates, it behaves pretty much like top, but for
>> interrupts.
>> It's quite a simple thing, that I tried to enhance a bit with
>> some cool features:
>> + refresh period can be specified.
>> + two display modes: display interrupts for every CPU, or only a
>> sum of all CPU.
>> + display every interrupt (sorted like /proc/interrupts), or
>> only active interrupts (sorted by activity).
>> + in case the number of interrupts changes during the execution
>> of itop (due to a rmmod/modprobe), it's handled without any fuss.
>> + command-line options are also available as hotkeys for
>> convenience.
>> + at last, the program display a summary on exit. The idea is
>> that this summary could be copied/pasted in emails to help debugging.
>>
>> If anyone is interested, feel free to try and comment !
>>
>> Cheers
>> _______________________________________________
>> Linux-audio-dev mailing list
>> Linux-audio-dev@email-addr-hidden
>> <mailto:Linux-audio-dev@email-addr-hidden>
>> http://lists.linuxaudio.org/listinfo/linux-audio-dev
>>
>>
>

_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-dev
Received on Tue Apr 22 00:15:02 2014