From: Peter Zijlstra <peterz@infradead.org>
To: Geoff Thorpe <geoff@geoffthorpe.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched: track "isolated" cpus like other cpu masks.
Date: Mon, 23 May 2011 22:14:09 +0200 [thread overview]
Message-ID: <1306181649.2497.1.camel@laptop> (raw)
In-Reply-To: <1305923374-13274-1-git-send-email-geoff@geoffthorpe.net>
On Fri, 2011-05-20 at 16:29 -0400, Geoff Thorpe wrote:
> When a subset of cpus have been isolated, it can be useful for subsystems
> or drivers that have cpu-affinity concerns to have access to this mask
> (just like the other cpu masks; "possible", "present", "active" and
> "online"). Eg. to provide specific handling for isolated cpus, or to
> determine the non-isolated cpus (which is what sched.c uses it for).
Nobody should be using that, isolated CPUs is a 'feature' slated for
removal.
next prev parent reply other threads:[~2011-05-23 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 20:29 [PATCH] sched: track "isolated" cpus like other cpu masks Geoff Thorpe
2011-05-21 3:06 ` yaff2 support ym cheng
2011-05-23 20:14 ` Peter Zijlstra [this message]
2011-05-26 16:38 ` [PATCH] sched: track "isolated" cpus like other cpu masks Geoff Thorpe
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=1306181649.2497.1.camel@laptop \
--to=peterz@infradead.org \
--cc=geoff@geoffthorpe.net \
--cc=linux-kernel@vger.kernel.org \
/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