cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@brodo.de>
To: Bas Mevissen <ml@basmevissen.nl>
Cc: cpufreq@www.linux.org.uk
Subject: Re: cpufreq and 2.4.
Date: Mon, 18 Aug 2003 20:00:12 +0200	[thread overview]
Message-ID: <20030818180012.GA1824@brodo.de> (raw)
In-Reply-To: <3F40AEC8.3060306@basmevissen.nl>

On Mon, Aug 18, 2003 at 12:47:36PM +0200, Bas Mevissen wrote:
> >B) Difficult-to-understand cpufreq user interfaces
> >The /proc/cpufreq and /proc/sys/cpu interfaces are difficult to understand
> >and already deprecated in 2.6. Do we really want them to be added to a
> >stable kernel release?
> >
> 
> Well, what then? There is no sysfs in 2.4, so we need something else to 
> control the beast :-)
> 
> How feasable is it to "port" the sysfs _interface_ to /proc? It would 
> simplicate matters for users, cpufreqd and documentation as they only 
> needs to change the "working directory" for 2.4.
> 
> (Because sysfs is something completely different than /proc, it would 
> mean writing new code. But as 2.4 will be in use for a couple of years, 
> I think it is worth the trouble.)

This seems to be a somewhat reasonable approach. However, it needs to be
made clear that this interface will only be available on 2.4. kernels. /proc
is bloated in 2.4., and so I don't mind, but for 2.6++ it should be aimed at
removing unneccessary stuff from /proc, so I'd strongly oppose
forward-porting this interface to 2.6. 

Anyways, anyone willing to write the "cpufreq 2.4. sysfs-emulation /proc
interface"?

	Dominik

  parent reply	other threads:[~2003-08-18 18:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-17 15:35 cpufreq and 2.4 Dominik Brodowski
2003-08-18  7:39 ` Ducrot Bruno
2003-08-18 10:14   ` Bas Mevissen
2003-08-18 12:49     ` Ducrot Bruno
2003-08-18 13:21       ` Bas Mevissen
2003-08-18 10:47 ` Bas Mevissen
2003-08-18 10:57   ` Russell King
2003-08-18 12:13     ` Bas Mevissen
2003-08-18 18:10       ` Russell King
2003-08-18 18:00   ` Dominik Brodowski [this message]
2003-08-19  7:24     ` Ducrot Bruno
2003-08-19  8:58       ` Bas Mevissen
2003-08-19  8:45     ` Bas Mevissen
2003-08-19 11:42       ` Ducrot Bruno

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=20030818180012.GA1824@brodo.de \
    --to=linux@brodo.de \
    --cc=cpufreq@www.linux.org.uk \
    --cc=ml@basmevissen.nl \
    /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