From: David Rientjes <rientjes@google.com>
To: Paul Jackson <pj@sgi.com>
Cc: menage@google.com, miaox@cn.fujitsu.com,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] cpusets: update tasks' cpus_allowed and mems_allowed after CPU/NODE offline/online
Date: Wed, 4 Jun 2008 12:33:39 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0806041232190.22192@chino.kir.corp.google.com> (raw)
In-Reply-To: <20080604142540.6fa2bcc3.pj@sgi.com>
On Wed, 4 Jun 2008, Paul Jackson wrote:
> > That would identify both kthreads that have been created with a subsequent
> > call to set_cpus_allowed() or kthread_bind().
>
> Or do I misunderstand?
>
> If I am reading you correctly, then would it work to have a check in the
> cpuset code (rather than in the lower set_cpus_allowed() routine),
> where that check refused to move tasks out of the root cpuset if they
> were (1) kernel threads (mm NULL) and (2) had cpus_allowed that were a
> strict subset of the root cpusets 'cpus' (the online cpus).
>
No, because sched_setaffinity() can still move the threads.
next prev parent reply other threads:[~2008-06-04 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 2:05 Miao Xie
2008-06-04 9:30 ` Paul Menage
2008-06-04 9:58 ` Paul Menage
2008-06-04 17:22 ` Paul Jackson
2008-06-04 19:01 ` David Rientjes
2008-06-04 19:25 ` Paul Jackson
2008-06-04 19:33 ` David Rientjes [this message]
2008-06-04 19:42 ` Paul Jackson
2008-06-04 20:02 ` David Rientjes
2008-06-04 20:21 ` Paul Jackson
-- strict thread matches above, loose matches on Subject: below --
2008-06-02 8:33 Miao Xie
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=alpine.DEB.1.10.0806041232190.22192@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=miaox@cn.fujitsu.com \
--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
all inboxes | Powered by JetHome®