From: Nick Piggin <nickpiggin@yahoo.com.au>
To: dino@in.ibm.com
Cc: Paul Jackson <pj@sgi.com>, Simon Derr <Simon.Derr@bull.net>,
lkml <linux-kernel@vger.kernel.org>,
lse-tech <lse-tech@lists.sourceforge.net>,
Matthew Dobson <colpatch@us.ibm.com>,
Dipankar Sarma <dipankar@in.ibm.com>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 2/3] Dynamic sched domains (v0.6)
Date: Tue, 17 May 2005 16:25:37 +1000 [thread overview]
Message-ID: <42898E61.3060304@yahoo.com.au> (raw)
In-Reply-To: <20050517041219.GB4596@in.ibm.com>
Dinakar Guniguntala wrote:
> o Patch2 has updated cpusets documentation and the core update_cpu_domains
> function
> o I have also moved the dentry d_lock as discussed previously
>
Hi Dinakar,
patch1 looks good. Just one tiny little minor thing:
> +
> + lock_cpu_hotplug();
> + partition_sched_domains(&pspan, &cspan);
> + unlock_cpu_hotplug();
> +}
> +
I don't think the cpu hotplug lock isn't supposed to provide
synchronisation between readers (for example, it may be turned
into an rwsem), but only between the thread and the cpu hotplug
callbacks.
In that case, can you move this locking into kernel/sched.c, and
add the comment in partition_sched_domains that the callers must
take care of synchronisation (which without reading the code, I
assume you're doing with the cpuset sem?).
If you agree with that change, you can add an
Acked-by: Nick Piggin <nickpiggin@yahoo.com.au>
to patch 1 and send it to Andrew whenever you're ready (better
CC Ingo as well). If not, please discuss! :)
Thanks,
Nick
next prev parent reply other threads:[~2005-05-17 6:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 4:10 [RFT PATCH] Dynamic sched domains (v0.6) Dinakar Guniguntala
2005-05-17 4:12 ` [PATCH 2/3] " Dinakar Guniguntala
2005-05-17 6:25 ` Nick Piggin [this message]
2005-05-17 9:35 ` Dinakar Guniguntala
2005-05-17 4:14 ` [PATCH 3/3] " Dinakar Guniguntala
2005-05-18 5:53 ` [RFT PATCH] " Paul Jackson
2005-05-18 18:06 ` [Lse-tech] " Dinakar Guniguntala
2005-05-18 21:02 ` Paul Jackson
2005-05-18 21:04 ` Paul Jackson
2005-05-18 21:05 ` Paul Jackson
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=42898E61.3060304@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=Simon.Derr@bull.net \
--cc=akpm@osdl.org \
--cc=colpatch@us.ibm.com \
--cc=dino@in.ibm.com \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--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