From: Max Krasnyansky <maxk@qualcomm.com>
To: Paul Jackson <pj@sgi.com>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
akpm@linux-foundation.org, menage@google.com,
seto.hidetoshi@jp.fujitsu.com, laijs@cn.fujitsu.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] cpuset: clean up cpuset hierarchy traversal code
Date: Mon, 28 Jul 2008 10:20:18 -0700 [thread overview]
Message-ID: <488DFFD2.7070004@qualcomm.com> (raw)
In-Reply-To: <20080728010141.fbd33866.pj@sgi.com>
Paul Jackson wrote:
> Li Zefan wrote:
>> - q = kfifo_alloc(number_of_cpusets * sizeof(cp), GFP_KERNEL, NULL);
>
>
> The block comment for rebuild_sched_domains() states:
>
>> ... May take callback_mutex during
>> * call due to the kfifo_alloc() and kmalloc() calls.
>
> I suspect that mention of kfifo_alloc() is no longer correct,
> with your patch. If so, perhaps you could send a little additional
> fix patch, to remove that mention from the comment.
>
Paul, please take a look at
cpuset: Rework sched domains and CPU hotplug handling
patch I sent out last week.
I'd appreciate if we applied that one first. It simplifies lock nesting
and rearranges the way sched domains are rebuilt. It is IMO a bit higher
priority than this patch because scheduler depends on the
rebuild_sched_domains() call and we have to call rebuild_sched_domains()
from cpu hotplug handlers.
Max
next prev parent reply other threads:[~2008-07-28 17:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 2:47 [PATCH 1/3] cpuset: clean up cpuset hierarchy traversal code Li Zefan
2008-07-28 4:37 ` Paul Jackson
2008-07-28 5:12 ` Paul Jackson
2008-07-29 1:44 ` Li Zefan
2008-07-28 6:01 ` Paul Jackson
2008-07-28 17:20 ` Max Krasnyansky [this message]
2008-07-29 1:25 ` Li Zefan
2008-07-30 10:12 ` Paul Jackson
2008-07-29 1:30 ` Li Zefan
2008-07-29 13:04 ` 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=488DFFD2.7070004@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=akpm@linux-foundation.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=pj@sgi.com \
--cc=seto.hidetoshi@jp.fujitsu.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