From: Andrew Morton <akpm@osdl.org>
To: Paul Jackson <pj@sgi.com>
Cc: "Siddha, Suresh B" <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: Tue, 15 Aug 2006 21:47:18 -0700 [thread overview]
Message-ID: <20060815214718.00814767.akpm@osdl.org> (raw)
In-Reply-To: <20060815212455.c9fe1e34.pj@sgi.com>
On Tue, 15 Aug 2006 21:24:55 -0700
Paul Jackson <pj@sgi.com> wrote:
> Thanks for the cleanup patch resend, Suresh.
>
> > Resending the new patch. Before patch had some issues for Andy and hence
> > dropped.
> >
> > Andrew, Please add this to -mm. This patch is against 2.6.18-rc4.
> > There might be a small conflict while applying to -mm. Let me know if you
> > want a patch on top of -mm.
> >
> > thanks,
> > suresh
> >
> > --
>
> I found the above patch commentary frustrating to read, as it told me
> very little, and teased me with reference to details that are left
> unsaid.
>
> Can we work on this patch's opening text a bit more?
Believe it or not, I usually suffer in silence.
>
> ..
>
> > + * cpu_power indicates the computing power of each sched group. This is
> > + * used for distributing the load between different sched groups
> > + * in a sched domain.
>
> Thanks for explaining what cpu_power means.
>
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.
next prev parent reply other threads:[~2006-08-16 4:50 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 [this message]
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
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=20060815214718.00814767.akpm@osdl.org \
--to=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.