public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: 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: Thu, 17 Aug 2006 12:18:04 -0700	[thread overview]
Message-ID: <20060817121804.e140f19e.pj@sgi.com> (raw)
In-Reply-To: <20060817110317.A14787@unix-os.sc.intel.com>

Suresh wrote:
> Let me resist the temptation and not go into the definition of horsepower
> here. You can refer any dictionary.

Good point <grin>.

Horsepower is a measure of power, of energy over time, such as the
rate of providing or using electrical or mechanical energy.

So, with your suggestion of 'horsepower', are you saying that cpu_power
is a metric of such electrical or mechanical energy -- the peak or
average watts of the electricity consumed by the CPUs in a group?

Or is 'cpu_power' a metric of the computational capacity, such as
BogoMIPS provided by the CPUs in a group, such as I had presumed?

Hmmm ... apparently from your latest explanation, it's neither
of these.

Rather it's a metric of how many tasks to place in a group, due to
various capacities and constraints, such as computational power
(BogoMIPS) and electrical power (watts or horsepower).

Should 'cpu_power' be renamed to 'task_load' ?

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

  reply	other threads:[~2006-08-17 19:18 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 [this message]
2006-08-17 23:29             ` Ian Stirling
2006-08-17 23:35               ` Paul Jackson
2006-08-17 23:56         ` Peter Williams
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=20060817121804.e140f19e.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=akpm@osdl.org \
    --cc=apw@shadowen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nickpiggin@yahoo.com.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox