>>> HZ on x86 for user space is defined as 100. Its a procps problem
>> Slight error in my initial diagnosis of why procps is getting Hertz
>> wrong tho. It's not because timer interrupts are only happening
>> on one CPU. It's because it thinks I have 4 CPUs per system, when
>> really I only have 2 CPUs per system.
> procps is still wrong.
> HZ on x86 is 100 by default.
> that isn't 100 per CPU, but 100 per second, regardless of whether the timer
> interrupt is distributed between CPUs or serviced on a single CPU.
No shit. Now, how do you create a ps executable that handles
a 2.4.xx kernel with a modified HZ value? People did this all
the time. I got many bug reports from these people, so don't
go saying they don't exist. Remember: one executable, running
on both of the these:
2.2.xx i386 as shipped by Linus
2.4.xx i386 with HZ modified
Come on, write the code if you think it's so easy.
You get bonus points for supporting 2.0.xx kernels
and the IA-64 kernel with that same executable.
Maybe you think I should tell these people to go to Hell?
In that case, what about the Alpha systems that ran HZ at
1200 instead of 1024?
I really wonder why people love to torment me for having the
decency to support systems that aren't 100% Linus-compliant.
Do you people burn idols for Linus, or only kiss his butt?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/