> 2) To use MHz or something else? The problem is that the number here is
> virtually meaningless. It does not translate from machine to machine,
> processor to processor, or application to application. So, if you have to
> pick a meaningless metric, what do you use? I would actually argue for % of
> full capacity instead of MHz, but it doesn't really matter in the end.
Percentages don't buy you much because they are as meaningless as
MHz numbers, or even more so. Percentages don't translate from
machine to machine either. One machine might find 50% speed
useful for power saving, another might want 33%. A third
one might work fine with 75% to prevent overheating.
An MHz carries more meaning - it is a measurable frequency.
Manufacturers tend to specify numbers in MHz.
Percentage of "full" is more problematic because "full"
isn't that well-defined.
Consider things like overclocking. That isn't merely a
hack - AMD specifies different max speeds for different
temperatures. I.e. they officially support higher
clock speed when using liquid cooling. The speed rating
stored in the cpu is only for the fan-cooling case.
Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/