From: Bruno Ducrot <ducrot@poupinou.org>
To: Wayne Wylupski <wayne@connact.com>, cpufreq@www.linux.org.uk
Subject: Re: userspace not supported for longrun?
Date: Wed, 2 Jun 2004 15:28:04 +0200 [thread overview]
Message-ID: <20040602132804.GC13782@poupinou.org> (raw)
In-Reply-To: <20040602121916.GA8781@dominikbrodowski.de>
On Wed, Jun 02, 2004 at 02:19:17PM +0200, Dominik Brodowski wrote:
> On Tue, Jun 01, 2004 at 07:52:05PM -0400, Wayne Wylupski wrote:
> > Thank you. The issue is that Fedora Core 2 ships with 'cpuspeed' as a
> > service, which fails on machines with Crusoe chips because it assumes
> > there's a userspace governor without first checking whether there it is
> > available.
> >
> > Would it really violate patents if the userspace governor were allowed
> > to work along the existing policies ("powersave" and "performance")?
>
> No, that's a purely technical issue: The Crusoe chip can only be set to a
> _frequency range_, and the chip itself (actually, the Code Morphing
> Software) decides which actual frequency is best for the current workload.
You can run a crusoe chip on a fixed frequency.
Some people also think that on some situation, the longrun will consume
more power than their algorithm (search for "vertigo OSDI2002", I don't
remmeber the exact link) for an example.
Of course the userspace stuff is completely useless anyway.
Cheers,
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2004-06-02 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 3:40 userspace not supported for longrun? Wayne Wylupski
2004-06-01 9:31 ` Bruno Ducrot
2004-06-01 23:52 ` Wayne Wylupski
2004-06-02 9:30 ` Bruno Ducrot
2004-06-02 12:19 ` Dominik Brodowski
2004-06-02 13:28 ` Bruno Ducrot [this message]
2004-06-03 4:18 ` Wayne Wylupski
2004-06-02 15:39 ` Francesco Poli
2004-06-02 12:40 ` 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=20040602132804.GC13782@poupinou.org \
--to=ducrot@poupinou.org \
--cc=cpufreq@www.linux.org.uk \
--cc=wayne@connact.com \
/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