From: Peter Williams <pwil3058@bigpond.net.au>
To: Paul Jackson <pj@sgi.com>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org,
nickpiggin@yahoo.com.au, mingo@redhat.com, apw@shadowen.org
Subject: Re: [patch] sched: group CPU power setup cleanup
Date: Fri, 18 Aug 2006 09:56:00 +1000 [thread overview]
Message-ID: <44E50210.4060102@bigpond.net.au> (raw)
In-Reply-To: <20060817102030.f8c41330.pj@sgi.com>
Paul Jackson wrote:
>>> Hope not. To me, "computing power" means megaflops/sec, or Dhrystones
>>> (don't ask) or whatever. If that's what "cpu_power" is referring to then
>>> the name is hopelessly ambiguous with peak joules/sec and a big renaming is
>>> due.
>> It refers to group's processing power. Perhaps "horsepower" is better term.
>
> Well ... I don't think "horsepower" is a step in the right direction.
>
> Andrew's point was over the word "power", not "cpu". The term
> "cpu_power" suggested to him we were concerned with the power supply
> watts consumed by a group of CPUs. Indeed, both those concerned with
> laptop battery lifetimes, and the air conditioning tonnage needed
> for big honkin NUMA iron might have reason to be concerned with the
> power consumed by CPUs.
>
> Changing the word "cpu" to "horse", but keeping the word "power",
> does nothing to address Andrew's point. Rather it just adds more
> confusion. We are obviously dealing with CPUs here, not horses.
>
> My understanding is that the "cpu_power" of the cpus in a sched group
> is rougly proportional to the BogoMIPS of the CPUs in that group.
>
How about energy instead of power? I.e. the CPU's capacity to do work.
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next prev parent reply other threads:[~2006-08-17 23:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 0:55 [patch] sched: group CPU power setup cleanup Siddha, Suresh B
2006-08-16 4:24 ` Paul Jackson
2006-08-16 4:47 ` Andrew Morton
2006-08-16 5:53 ` Paul Jackson
2006-08-16 18:03 ` Siddha, Suresh B
2006-08-17 17:20 ` Paul Jackson
2006-08-17 18:03 ` Siddha, Suresh B
2006-08-17 19:18 ` Paul Jackson
2006-08-17 23:29 ` Ian Stirling
2006-08-17 23:35 ` Paul Jackson
2006-08-17 23:56 ` Peter Williams [this message]
2006-08-18 4:15 ` Paul Mackerras
2006-08-16 17:45 ` Siddha, Suresh B
2006-08-18 21:23 ` [patch] sched: generic sched_group cpu power setup Siddha, Suresh B
2006-08-18 22:29 ` Paul Jackson
2006-08-18 22:42 ` Siddha, Suresh B
2006-08-19 0:09 ` Paul Jackson
2006-08-21 22:19 ` Siddha, Suresh B
-- strict thread matches above, loose matches on Subject: below --
2006-06-30 0:31 [Patch] sched: group CPU power setup cleanup Siddha, Suresh B
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=44E50210.4060102@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nickpiggin@yahoo.com.au \
--cc=pj@sgi.com \
--cc=suresh.b.siddha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.