From: Ingo Molnar <mingo@elte.hu>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Gautham R Shenoy <ego@in.ibm.com>, Paul Jackson <pj@sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched: missing locking in sched_domains code
Date: Mon, 28 Apr 2008 10:32:22 +0200 [thread overview]
Message-ID: <20080428083222.GA16963@elte.hu> (raw)
In-Reply-To: <20080428081129.GC4507@osiris.boeblingen.de.ibm.com>
* Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
> /* doms_cur_mutex serializes access to doms_cur[] array */
> static DEFINE_MUTEX(doms_cur_mutex);
>
> +static inline void lock_doms_cur(void)
> +{
> + mutex_lock(&doms_cur_mutex);
> +}
> @@ -7813,8 +7811,10 @@ int arch_reinit_sched_domains(void)
> int err;
>
> get_online_cpus();
> + lock_doms_cur();
thanks, that looks a lot more clean already. May i ask for another
thing, if you are hacking on this anyway? Please get rid of the
lock_doms_cur() complication now that it's not conditional - an open
coded mutex_lock(&sched_doms_mutex) looks more readable - it gives a
clear idea about what's happening. Also, please rename sched_doms_mutex
to something less tongue-twisting - such as sched_domains_mutex. Hm?
Ingo
next prev parent reply other threads:[~2008-04-28 8:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 21:12 Heiko Carstens
2008-04-28 1:39 ` Andrew Morton
2008-04-28 7:09 ` Heiko Carstens
2008-04-28 7:24 ` Ingo Molnar
2008-04-28 7:28 ` Andrew Morton
2008-04-28 7:52 ` Heiko Carstens
2008-04-28 8:11 ` Heiko Carstens
2008-04-28 8:32 ` Ingo Molnar [this message]
2008-04-28 8:49 ` Heiko Carstens
2008-04-28 8:57 ` Andrew Morton
2008-04-28 9:17 ` Heiko Carstens
2008-04-28 9:31 ` Andrew Morton
2008-04-28 9:33 ` Heiko Carstens
2008-04-28 12:27 ` Ingo Molnar
2008-04-28 13:13 ` Ingo Molnar
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=20080428083222.GA16963@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=ego@in.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.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