Kaigai Kohei wrote:
> Indeed, I tried to include the CpuSet into PAGG.
Could you describe more what CpuSet patch this is that you are including
in PAGG?
I have a cpuset patch in Andrew Morton's *-mm patch series for several
months now, but I have not thought that it was a good candidate customer
of PAGG, for the main reason that my cpuset patch requires other kernel
changes, in the kernel memory allocator, and in the other calls that
manipulate scheduling (sched_setaffinity) and memory placement (mbind,
set_mempolicy), as well as in the /proc file system. See the added
kernel files include/linux/cpuset.h and kernel/cpuset.c, for the central
portions of the cpuset patch in any *-mm release of the last few months.
My understanding of PAGG is that it is especially useful in supporting
loadable modules that require to construct some grouping of the tasks on
a system, and that require to take some actions on key task events such
as fork and exit. Since the cpuset's that I know require several
additional specialized hooks not provided by PAGG, I have concluded that
PAGG is not a valuable base for cpusets. I have also concluded that
cpuset's is not a potential loadable module -- too many kernel hooks
required.
Are you referring to these cpusets, or about some other facility by
that name?
If you are referring to these same cpusets, then what benefit do you
consider that PAGG provides to these cpusets?
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@xxxxxxx> 1.650.933.1373, 1.925.600.0401
|