[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 30 Jul 2007 10:33:17 -0700
From: Sven-Thorsten Dietrich <sdietrich@...ell.com>
To: "H. Peter Anvin" <hpa@...or.com>, akpm@...ux-foundation.org
Cc: Joe Korty <joe.korty@...r.com>, mingo@...e.hu, tglx@...utronix.de,
linux-rt-users@...r.kernel.org, linux-kernel@...r.kernel.org,
jason.baietto@...r.com
Subject: Re: [PATCH] create /proc/all-interrupts
On Thu, 2007-07-26 at 11:56 -0700, H. Peter Anvin wrote:
> Joe Korty wrote:
> > Create /proc/all-interrupts for some architectures.
> >
> > Create a version of /proc/interrupts that displays _every_
> > IRQ vector, not just those that someone thought might be
> > interesting, and add an entry in the commentary column
> > for those vectors which lacked such a comment.
> >
> > Rationale: /proc/interrupts is not truly useful unless it
> > displays every IRQ vector, not just those somebody thought
> > would be interesting. For example, since /proc/interrupts
> > does not display the rescheduling interrupt, the occurance
> > of rescheduling interrupt floods ends up affecting
> > latencies, yet without an entry in /proc/interrupts, it
> > is difficult to discern why latencies are being affected.
> >
> > Rather than modify /proc/interrupts, this patch creates
> > a new version of /proc/interrupts, on the off-chance
> > that adding new lines to /proc/interrupts, and appending
> > new fields to the end of old lines, might break some
> > longstanding script. However, these kinds of changes
> > traditionally do not affect scripts, so it might be
> > reasonable to fold /proc/all-interrupts back into
> > /proc/interrupts.
>
> I think that would be the right thing to do. We have added things to
> /proc/interrupts in the past.
>
Hi Andrew,
Would it make sense to drop this patch into -mm for feedback?
Thanks,
Sven
Content of type "message/rfc822" skipped
Powered by blists - more mailing lists