<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi,<br>
<br>
I guess you're right, I could change the name.<br>
I liked the name itop, it sounds good, and it's the perfect name
for this soft. That's why people already used it before.<br>
<br>
But I think I'll rename it to 'inttop', it's pretty much the same,
and it tell what it does.<br>
<br>
Cheers<br>
<br>
<br>
<br>
On 05/26/2013 07:59 PM, Diego Veralli wrote:<br>
</div>
<blockquote
cite="mid:CAF1--ZCQYmdj9ZOgo2aFxkw3v+8MEeP1hNaX-B8pRyozPKT+0g@mail.gmail.com"
type="cite">Hey elboulangero, <br>
<br>
You might want to change the name, there are already 2 itops that
I know of, that monitor interrupts:<br>
<br>
* <a moz-do-not-send="true"
href="http://packages.debian.org/wheezy/itop">http://packages.debian.org/wheezy/itop</a><br>
* <a moz-do-not-send="true"
href="http://et.redhat.com/%7Ejmh/tools/xen/itop">http://et.redhat.com/~jmh/tools/xen/itop</a>
(this is just a small perl script, but still...)<br>
<br>
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.. <br>
<br>
Cheers<br>
Diego<br>
<br>
<div class="gmail_quote">On Fri, May 10, 2013 at 12:15 AM,
elboulangero <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:elboulangero@gmail.com" target="_blank">elboulangero@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hello
everyone,<br>
<br>
lately I had to fight big XRUN troubles, and thanks to this
forum I finally solved that. This excellent thread saved me:<br>
<a moz-do-not-send="true"
href="http://linuxaudio.org/mailarchive/lau/2012/9/5/192706"
target="_blank">http://linuxaudio.org/mailarchive/lau/2012/9/5/192706</a><br>
<br>
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.<br>
<br>
So, I ended up writing my own tool to monitor the file
/proc/interrupts.<br>
It's available a this address:<br>
<a moz-do-not-send="true"
href="https://gitorious.org/elboulangero/itop"
target="_blank">https://gitorious.org/elboulangero/itop</a><br>
<br>
As its name indicates, it behaves pretty much like top, but
for interrupts.<br>
It's quite a simple thing, that I tried to enhance a bit with
some cool features:<br>
+ refresh period can be specified.<br>
+ two display modes: display interrupts for every CPU, or
only a sum of all CPU.<br>
+ display every interrupt (sorted like /proc/interrupts), or
only active interrupts (sorted by activity).<br>
+ in case the number of interrupts changes during the
execution of itop (due to a rmmod/modprobe), it's handled
without any fuss.<br>
+ command-line options are also available as hotkeys for
convenience.<br>
+ at last, the program display a summary on exit. The idea is
that this summary could be copied/pasted in emails to help
debugging.<br>
<br>
If anyone is interested, feel free to try and comment !<br>
<br>
Cheers<br>
_______________________________________________<br>
Linux-audio-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:Linux-audio-dev@lists.linuxaudio.org"
target="_blank">Linux-audio-dev@lists.linuxaudio.org</a><br>
<a moz-do-not-send="true"
href="http://lists.linuxaudio.org/listinfo/linux-audio-dev"
target="_blank">http://lists.linuxaudio.org/listinfo/linux-audio-dev</a><br>
</blockquote>
</div>
<br>
</blockquote>
<br>
</body>
</html>