Thanks for doing this, Nick. One area looks like some details
need working.
Nick Andrew wrote:
> config PROC_PID_CPUSET
> bool "Include legacy /proc/<pid>/cpuset file"
> depends on CPUSETS
> default y
> + help
> + This option provides the legacy /proc/<pid>/cpuset file.
> +
> + It has been deprecated in favour of an additional line
> + in /proc/<pid>/status showing on which CPUs a process
> + may be scheduled.
I don't think /proc/<pid>/cpuset (PROC_PID_CPUSET) is, or should be,
deprecated.
Actually, I'd be inclined toward removing this CONFIG option, and
making /proc/<pid>/cpuset a non-optional consequence of enabling
cpusets ... so I'm adding Paul Menage to the CC list, in case he has
thoughts or insights on this. The duplication of this bit of information
between both /proc/<pid>/cpuset and one line of /proc/<pid>/status is a
minor and harmless wart, resulting from the evolution of cgroups from
cpusets, that is not worth bothering kernel configuration users with
questions about.
And isn't that a line in /proc/<pid>/cgroup, not in /proc/<pid>/status ?
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[EMAIL PROTECTED]> 1.940.382.4214
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
