On Mon, Jun 23, 2014 at 4:15 PM, Pavel Machek pavel@ucw.cz wrote:
Hi!
> I guess better interface would be something like > > pstate/07/core_clock_min > core_clock_max > memory_clock_min > memory_clock_max > > and then pstate/active containing just the number of active state?
Could we just say that the format of this file is one-per-line of
level: information-for-the-user
But it is not.
But it is...
Management tools will want to parse it, sooner or later. What is wrong with solution described above?
It is complex and annoying to the people that will actually use it.
grep -r . pstate/ is actually not that bad...
While that's a clever trick that anyone who's done a bunch of stuff with sysfs knows, I doubt the average linux user could come up with that on their own. I know I didn't.
And yes, some kind of utility to select right performance level would be nice in future... Or maybe not. Perhaps in not so distant future kernel will use right performance level for given load...?
Eventually yes. Currently switching between levels varies from unsupported to unreliable depending on the hardware (as in, hangs the card, or does otherwise-not-great things). Automatic switching requires regular switching to be reliable :) [And the performance counters that are presently being worked on to be able to tell the card load.]
-ilia