From: Pavel Machek <pavel@ucw.cz>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: Greg KH <greg@kroah.com>,
kernel list <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Ben Skeggs <bskeggs@redhat.com>
Subject: Re: unparseable, undocumented /sys/class/drm/.../pstate
Date: Mon, 23 Jun 2014 22:15:03 +0200 [thread overview]
Message-ID: <20140623201503.GA4551@amd.pavel.ucw.cz> (raw)
In-Reply-To: <CAKb7UvhmatCtu2rEHgVOjitN1gAPTsgfaUmA2iOLX2Qwhi+Yxg@mail.gmail.com>
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...
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...?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2014-06-23 20:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-21 18:02 unparseable, undocumented /sys/class/drm/.../pstate Pavel Machek
2014-06-21 18:22 ` Ilia Mirkin
2014-06-21 18:50 ` Pavel Machek
2014-06-21 19:34 ` Ilia Mirkin
2014-06-21 19:45 ` Greg KH
2014-06-23 2:12 ` Ilia Mirkin
2014-06-23 13:02 ` Pavel Machek
2014-06-23 13:29 ` Ilia Mirkin
2014-06-23 20:15 ` Pavel Machek [this message]
2014-06-23 20:18 ` Ilia Mirkin
2014-06-23 20:26 ` Greg KH
2014-06-23 20:32 ` Ilia Mirkin
2014-06-24 0:06 ` Ben Skeggs
2014-06-24 16:00 ` Greg KH
2014-06-23 16:07 ` Greg KH
2014-06-23 16:18 ` Ilia Mirkin
2014-06-23 16:36 ` Greg KH
2014-06-23 16:40 ` Ilia Mirkin
2014-06-23 17:46 ` Martin Peres
2014-06-23 17:56 ` Ilia Mirkin
2014-06-23 18:00 ` Martin Peres
2014-06-23 18:05 ` Ilia Mirkin
2014-06-23 18:09 ` Greg KH
2014-06-23 18:08 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140623201503.GA4551@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=greg@kroah.com \
--cc=imirkin@alum.mit.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).