mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: akpm@osdl.org, suresh.b.siddha@intel.com,
	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 10:20:30 -0700	[thread overview]
Message-ID: <20060817102030.f8c41330.pj@sgi.com> (raw)
In-Reply-To: <20060816110357.B7305@unix-os.sc.intel.com>

> > 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.

-- 
                  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 17:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16  0:55 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 [this message]
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
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=20060817102030.f8c41330.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

Powered by JetHome