Re: [PATCH] Revert 9fc2105aeaaf56b0cf75296a84702d0f9e64437b to fix pyaudio (and probably more)

From: Linus Torvalds
Date: Wed Jan 07 2015 - 19:57:38 EST


On Wed, Jan 7, 2015 at 4:45 PM, Nicolas Pitre <nicolas.pitre@xxxxxxxxxx> wrote:
>
> Would you mind if on ARM we used the bogomips line as an informative
> approximation for the CPU speed? After all, this is the meaning it had
> for nearly 20 years. And unlike on X86 we don't have the actual CPU
> clock in there. And that's still the meaning it has on most ARM systems
> out there.

Yes, I actually would mind, unless you have a damn good reason for it.

On x86, we have bogomips, but we also have this line:

cpu MHz : 2275.109

and I really don't see why you should lie in your /proc/cpuinfo.

Really.

Just give the real information. Don't lie.

Quite frankly, the *only* actual real reason I've heard from you for
not having the real bogomips there is "waste of time".

And this whole thread has been *nothing* but waste of time. But it has
been *you* wasting time, and that original commit. If you had just
left it alone, and had just let the revert do its job, none of this
waste of time would have happened.

So quite frankly, my patience for you arguing "wasting time" is pretty
damn low. I think your arguments are crap, I still think your NAK was
*way* out of line, and I think it's completely *insane* to lie about
bogomips. It's disasteful, it's dishonest, and there's no reason for
it.

If you want to give people a sense of the CPU frequency, then dammit,
just *do* that. Add that "cpu MHz" line that we already have on x86.

Seriously, what kind of *insane* argument can you really marshal for
lying to users?

And if you want users to know the CPU frequency, then why the f*ck
would you call it "bogomips" and confuse them?

Christ, this whole thing is annoying. I really find it *offensive* how
you want to basically lie to users.

Stop this idiocy. Really. There is no excuse.

Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/