From: "Paul Menage" <menage@google.com>
To: miaox@cn.fujitsu.com
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
"Paul Jackson" <pj@sgi.com>,
"David Rientjes" <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 02:58:09 -0700 [thread overview]
Message-ID: <6599ad830806040258h552e4623m5efae8202c5d026d@mail.gmail.com> (raw)
In-Reply-To: <6599ad830806040230l24bd1201y3cc0ea0273d835ad@mail.gmail.com>
On Wed, Jun 4, 2008 at 2:30 AM, Paul Menage <menage@google.com> wrote:
> On Tue, Jun 3, 2008 at 7:05 PM, Miao Xie <miaox@cn.fujitsu.com> wrote:
>>
>> Maybe we need to add a flag in the task_struct to mark which task can't be
>> unbound?
>
> Yes, something like a PF_CPU_BOUND flag that gets set in
> kthread_bind() and checked for in set_cpus_allowed() would be the
> right way to handle that. We have an internal change like that against
> an older kernel verison - I'll see if I can find someone to forward
> port it and send it in.
And in fact they already did, and sent it to lkml a few months ago:
http://marc.info/?l=linux-kernel&m=120419372032623
Paul
next prev parent reply other threads:[~2008-06-04 9:58 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 [this message]
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
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=6599ad830806040258h552e4623m5efae8202c5d026d@mail.gmail.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaox@cn.fujitsu.com \
--cc=pj@sgi.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 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®