mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mattia Dongili <malattia@linux.it>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Alejandro Bonilla <abonilla@linuxwireless.org>,
	Jeff Garzik <jeff@garzik.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Dual Core on Linux questions
Date: Thu, 23 Mar 2006 18:55:58 +0100	[thread overview]
Message-ID: <20060323175558.GA4386@inferi.kami.home> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB6007A24C46@scsmsx403.amr.corp.intel.com>

Hi,

On Wed, Mar 22, 2006 at 07:36:42PM -0800, Pallipadi, Venkatesh wrote:
[...]
> minima changes required in cpufreqd if any.
> Options:
> 1) Multiple core can manage frequency independently: In this case,
> cpufreq exports separate interfaces for each cpu in
> /sys/devices/system/cpu/cpuX. So, cpufreqd should work as it would work
> on an SMP system (Assuming that cpufreqd works fine on an SMP system
> today ;-))

hehe, this is exactely where cpufreqd needs some work as it doesn't
distinguish between UP and MP currently, it just applies the same
cpufreq policy  to all available processors.
But I'm already working on this.

> 2) Multiple cores can be at a single frequency, but hardware will
> coordinate between two cores internally (pick the highest frequency
> request from two cores and run both of them at that frequency). This
> will be very much similar to 1, in the way in which cpufreq and kernel
> handles it.

cpufreqd has no problems here.

> 3) Multiple cores can be at a single frequency and hardware depends on
> OS to do the coordination, pick the maximum of all the requests from the
> cores and set the frequency using appropriate hardware interface. This
> is the case, where cpufreqd may need a change. In this case, say CPU 0
> and 1 are two different cores on same package and they share frequency
> and OS has to coordinate the freq request from these two CPUs. In this
> case, /sys/devices/system/cpu/cpu1/cpufreq will be kind of a symbolic
> link to /sys/devices/system/cpu/cpu0/cpufreq. Cpufreq tells that these
> two are dependent by using "affected_cpus" in the same sysfs directory

yes, cpufreqd needs some work on this, but it will be easily handled
once 1) is done and anyway it is't that bad here currenlty, it will
just write to both .../cpu0 and .../cpu1 the same profile.

> (in this case "0 1"). Now, if cpufreqd does a set_speed on cpu0 and
> cpu1, both CPUs will be affected. Cpufreqd should be aware that these
> CPUs are dependent and change freq based on maximum utilization of these
> two CPUs.

Oh, there's the ondemand governor for this. 
A little digression though just to point out that cpufreqd works
differently from cpuspeed, speedfreq et al.
It collects system status data (acpi/apm/pmu data, cpu load,
sensors data,...) and applies a cpufreq policy based on user defined
rules (eg: when battery is between 5% and 50% and ac is unplugged run
with ondemand @ 40%-70% - quite like the old speestep applet I found on
win2k on this laptop some years ago).
No best frequency caclulation is done, too many parameters and for just
the cpu load we have the excellent ondemand governor.

Thanks for the useful insight!
-- 
mattia
:wq!

  parent reply	other threads:[~2006-03-23 17:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-23  3:36 Pallipadi, Venkatesh
2006-03-23  3:44 ` Jeff Garzik
2006-03-29 19:51   ` Bill Davidsen
2006-03-30 20:31     ` Jeff Garzik
2006-04-04 19:30       ` Bill Davidsen
2006-03-23 17:55 ` Mattia Dongili [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-23  3:51 Pallipadi, Venkatesh
2006-03-18  8:35 Alejandro Bonilla
2006-03-18  8:58 ` Jeff Garzik
2006-03-18  9:03   ` Alejandro Bonilla
2006-03-18 10:49     ` Mattia Dongili
2006-03-18  9:21 ` Arjan van de Ven
2006-03-20 19:23 ` Wes Felter

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=20060323175558.GA4386@inferi.kami.home \
    --to=malattia@linux.it \
    --cc=abonilla@linuxwireless.org \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@intel.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

all inboxes | Powered by JetHome®