Re: [PATCH 2/2] cpusets: update tasks' cpus_allowed andmems_allowed after CPU/NODE offline/online

[Paul Jackson]

Paul M, quoting Miao Xie <miaox@xxxxxxxxxxxxxx>:
>>
>> 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@xxxxxxx> 1.940.382.4214
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/