From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "'Ingo Molnar'" <mingo@elte.hu>, "Con Kolivas" <kernel@kolivas.org>
Cc: "'Andrew Morton'" <akpm@osdl.org>,
"'Nick Piggin'" <nickpiggin@yahoo.com.au>,
"'Chris Mason'" <mason@suse.com>, <linux-kernel@vger.kernel.org>
Subject: RE: [patch] fix smt nice lock contention and optimization
Date: Sat, 3 Jun 2006 01:12:04 -0700 [thread overview]
Message-ID: <000801c686e5$666e5f60$df34030a@amr.corp.intel.com> (raw)
In-Reply-To: <20060603075734.GC20229@elte.hu>
Ingo Molnar wrote on Saturday, June 03, 2006 12:58 AM
> * Con Kolivas <kernel@kolivas.org> wrote:
>
> > Could we make this neater with extra braces such as:
> >
> > for_each_domain(this_cpu, tmp) {
> > if (tmp->flags & SD_SHARE_CPUPOWER) {
> > sd = tmp;
> > break;
> > }
> > }
> >
> > and same for the other uses of for_each ? I know it's redundant but
> > it's neater IMO when there are multiple lines of code below it.
>
> yep, that's the preferred style when there are multiple lines below a
> loop.
OK, thanks for the tips. Here is an incremental coding-style fix:
--- ./kernel/sched.c.orig 2006-06-02 23:54:11.000000000 -0700
+++ ./kernel/sched.c 2006-06-02 23:55:45.000000000 -0700
@@ -2973,11 +2973,12 @@
struct sched_domain *tmp, *sd = NULL;
int i;
- for_each_domain(this_cpu, tmp)
+ for_each_domain(this_cpu, tmp) {
if (tmp->flags & SD_SHARE_CPUPOWER) {
sd = tmp;
break;
}
+ }
if (!sd)
return;
@@ -3019,11 +3020,12 @@
if (!p->mm || rt_task(p))
return 0;
- for_each_domain(this_cpu, tmp)
+ for_each_domain(this_cpu, tmp) {
if (tmp->flags & SD_SHARE_CPUPOWER) {
sd = tmp;
break;
}
+ }
if (!sd)
return 0;
next prev parent reply other threads:[~2006-06-03 8:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-03 7:43 Chen, Kenneth W
2006-06-03 7:49 ` Ingo Molnar
2006-06-03 8:11 ` Andrew Morton
2006-06-03 8:17 ` Chen, Kenneth W
2006-06-03 8:22 ` Andrew Morton
2006-06-03 7:52 ` Con Kolivas
2006-06-03 7:57 ` Ingo Molnar
2006-06-03 8:12 ` Chen, Kenneth W [this message]
2006-06-03 8:17 ` Con Kolivas
2006-06-03 8:52 ` Nick Piggin
2006-06-03 18:45 ` Chris Mason
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='000801c686e5$666e5f60$df34030a@amr.corp.intel.com' \
--to=kenneth.w.chen@intel.com \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.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
Powered by JetHome