From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Bruno Ducrot <ducrot@poupinou.org>
Cc: jeremy@goop.org, cpufreq@www.linux.org.uk
Subject: Re: [RFC] cpufreqtools
Date: Fri, 22 Oct 2004 19:47:45 +0200 [thread overview]
Message-ID: <20041022174745.GA12506@dominikbrodowski.de> (raw)
In-Reply-To: <20041022172109.GF22405@poupinou.org>
On Fri, Oct 22, 2004 at 07:21:09PM +0200, Bruno Ducrot wrote:
> On Fri, Oct 22, 2004 at 04:57:38PM +0200, Dominik Brodowski wrote:
> > On Fri, Oct 22, 2004 at 04:39:27PM +0200, Bruno Ducrot wrote:
> > > I think that Jeremy's work being somehow integrated into your utilities.
> > > I think libspeedfreq.c is a good starting point for point C at least.
> >
> > Unfortunately, I can't base the suggested cpufreqtools not on Jeremy's work,
> > as it mixes userspace with kernelspace policies... and doesn't use
> > libsysfs... However, updating speedfreq to use cpufreqtools seems to be
> > possible and will probably lead to a code reduction in speedfreq.
>
> I do like Jeremy's idea to wrap all sysfs stuff in one deamon, then
> all clients (via his library) will communicate with this daemon in
> order to set different policies.
This looks like an interesting idea _on top_ of the libcpufreq stuff I
suggest. Though, I'm not really convinced whether the overhead of a daemon is
needed, as it should be clear to the admin that different cpufreq userspace
tools running at the same time are a bad idea.
> So all you care is to secure
> this daemon, not random setuid programs that others may wrote.
not others, /me ;-) Which may make it worse, though...
Thanks,
Dominik
next prev parent reply other threads:[~2004-10-22 17:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 17:22 [RFC] cpufreqtools Dominik Brodowski
2004-10-21 18:51 ` Dave Jones
2004-10-22 14:39 ` Bruno Ducrot
2004-10-22 14:57 ` Dominik Brodowski
2004-10-22 17:21 ` Bruno Ducrot
2004-10-22 17:47 ` Dominik Brodowski [this message]
2004-10-22 18:19 ` Bruno Ducrot
2004-10-24 16:30 ` Jeremy Fitzhardinge
2004-10-25 10:07 ` Paul Ionescu
2004-10-26 19:57 ` Dominik Brodowski
2004-10-25 9:01 ` Mattia Dongili
2004-10-25 11:11 ` Dominik Brodowski
2004-10-25 12:17 ` Mattia Dongili
2004-10-25 12:42 ` Dominik Brodowski
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=20041022174745.GA12506@dominikbrodowski.de \
--to=linux@dominikbrodowski.de \
--cc=cpufreq@www.linux.org.uk \
--cc=ducrot@poupinou.org \
--cc=jeremy@goop.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