From: Paul Jackson <pj@sgi.com>
To: "Paul Menage" <menage@google.com>
Cc: miaox@cn.fujitsu.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, rientjes@google.com
Subject: Re: [PATCH 2/2] cpusets: update tasks' cpus_allowed and mems_allowed after CPU/NODE offline/online
Date: Wed, 4 Jun 2008 12:22:27 -0500 [thread overview]
Message-ID: <20080604122227.a092e70e.pj@sgi.com> (raw)
In-Reply-To: <6599ad830806040258h552e4623m5efae8202c5d026d@mail.gmail.com>
Paul M, quoting Miao Xie <miaox@cn.fujitsu.com>:
>>
>> Maybe we need to add a flag in the task_struct to mark which task can't be
>> unbound?
Do we need a new PF_* flag for this? Perhaps one can test for this
by examining the currently available properties of tasks. Would it
be sufficient to look for kernel threads (NULL mm_struct) whose
cpus_allowed is a strict subset of the online CPUs?
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.940.382.4214
next prev parent reply other threads:[~2008-06-04 17:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 2:05 [PATCH 2/2] cpusets: update tasks' cpus_allowed and mems_allowed after CPU/NODE offline/online Miao Xie
2008-06-04 9:30 ` Paul Menage
2008-06-04 9:58 ` Paul Menage
2008-06-04 17:22 ` Paul Jackson [this message]
2008-06-04 19:01 ` David Rientjes
2008-06-04 19:25 ` Paul Jackson
2008-06-04 19:33 ` David Rientjes
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=20080604122227.a092e70e.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=miaox@cn.fujitsu.com \
--cc=rientjes@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.