From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org, "Siddha,
Suresh B" <suresh.b.siddha@intel.com>,
nickpiggin@yahoo.com.au, mingo@elte.hu, pwil3058@bigpond.net.au,
akpm@osdl.org
Subject: Re: [Patch] sched: mc/smt power savings sched policy
Date: Tue, 6 Jun 2006 18:06:22 -0700 [thread overview]
Message-ID: <20060606180622.B18026@unix-os.sc.intel.com> (raw)
In-Reply-To: <200606070959.09216.kernel@kolivas.org>; from kernel@kolivas.org on Wed, Jun 07, 2006 at 09:59:08AM +1000
On Wed, Jun 07, 2006 at 09:59:08AM +1000, Con Kolivas wrote:
> This MC code is a maze of #ifdefs within functions and getting harder to
> follow with each subsequent patch. Can we not deviate so much from kernel
> style?
build_sched_domains() originally was not designed with this many sched
domains in mind.. I can take a look at cleaning up of the sched domains
setup..
thanks,
suresh
next prev parent reply other threads:[~2006-06-07 1:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 18:25 [Patch] sched: mc/smt power savings sched policy Siddha, Suresh B
2006-06-06 23:59 ` Con Kolivas
2006-06-07 1:06 ` Siddha, Suresh B [this message]
2006-06-07 16:49 ` Andrew Morton
2006-06-07 17:29 ` 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=20060606180622.B18026@unix-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pwil3058@bigpond.net.au \
/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