Re: 2.6.20-rc6-mm3

[Rob Landley <rob@landley.net>]

On Tuesday 06 February 2007 6:28 pm, Daniel Walker wrote:
> On Tue, 2007-02-06 at 18:15 -0500, Rob Landley wrote:
> > On Tuesday 06 February 2007 3:40 pm, Daniel Walker wrote:
> > > In this case "different" goes into userspace .. So different could mean
> > > userspace regression, which is something that we don't want. I have no
> > > idea if any apps use /proc/interrupts , but it's possible since it's
> > > been around for a long time.
> > > 
> > > The reason that I'm bringing it up at all is because people have ask me
> > > "Why isn't my timer ticking??"

Ah, you can't answer this question.  Right:

A) Because there are multiple timer interrupt sources in the system, and we're 
now using a newer (better) one.

B) This measures interrupts.  It doesn't measure jiffies.  Interrupts != 
jiffies.  This is a conceptual issue.

C) /proc/uptime may be of use here.

> > Because there are two clock sources in the machine and it's using the 
other 
> > one, so the interrupt isn't firing?
> > 
> > Are you saying that the /proc statistics aren't accurate, or that you 
> > previously misunderstood what it was actually measuring and you'd now like 
it 
> > to lie?
> 
> I understand exactly what is happening . The statistics are unclear, and
> tend to confuse people .

You find /proc/interrupts showing interrupts to be _unclear_?

> Daniel

Rob
-- 
"Perfection is reached, not when there is no longer anything to add, but
when there is no longer anything to take away." - Antoine de Saint-Exupery