From: Max Krasnyansky <maxk@qualcomm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Nish Aravamudan <nish.aravamudan@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Gregory Haskins <ghaskins@novell.com>,
Dimitri Sivanich <sivanich@sgi.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Using cpusets for configuration/isolation [Was Re: RT sched: cpupri_vec lock contention with def_root_domain and no load balance]
Date: Wed, 19 Nov 2008 08:31:56 -0800 [thread overview]
Message-ID: <49243F7C.9090109@qualcomm.com> (raw)
In-Reply-To: <20081119125135.GB20475@elte.hu>
Ingo Molnar wrote:
> * Max Krasnyansky <maxk@qualcomm.com> wrote:
>
>> What you described is almost exactly what I did in my original cpu
>> isolation patch, which did get NAKed :). Basically I used global
>> cpu_isolated_map and exposed 'isolated' bit, etc.
>
> Please extend cpusets according to the plan outlined by PeterZ a few
> months ago - that's the right place to do partitioning.
Already did. It's all in mainline. The part you quoted was just pointing out
that the original approach was not correct.
Max
next prev parent reply other threads:[~2008-11-19 16:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 19:23 Using cpusets for configuration/isolation [Was Re: RT sched: cpupri_vec lock contention with def_root_domain and no load balance] Nish Aravamudan
2008-11-19 1:59 ` Max Krasnyansky
2008-11-19 2:11 ` Nish Aravamudan
2008-11-19 5:14 ` Max Krasnyansky
2008-11-19 12:30 ` Gregory Haskins
2008-11-19 16:28 ` Max Krasnyansky
2008-11-19 22:11 ` Nish Aravamudan
2008-11-19 12:51 ` Ingo Molnar
2008-11-19 16:31 ` Max Krasnyansky [this message]
2008-11-19 17:44 ` Ingo Molnar
2008-11-19 20:01 ` Max Krasnyansky
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=49243F7C.9090109@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nish.aravamudan@gmail.com \
--cc=peterz@infradead.org \
--cc=sivanich@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;
as well as URLs for NNTP newsgroup(s).