Hirokazu Takahashi
2005-10-24 05:52:58 UTC
Hi Paul,
I realized CPUSETS has another problem around pdflush.
Some cpuset may make most of pages in it dirty, while the others don't.
In this case, pdflush may not start since the ratio of the dirty pages
in the box may be less than the watermark, which is defined globally.
This may probably make it hard to allocate pages from the cpuset
or the nodes it depends on. This wouldn't be good for NUMA machine
without cpusets either.
Do you have any plans about it?
Hirokazu Takahashi.
I realized CPUSETS has another problem around pdflush.
Some cpuset may make most of pages in it dirty, while the others don't.
In this case, pdflush may not start since the ratio of the dirty pages
in the box may be less than the watermark, which is defined globally.
This may probably make it hard to allocate pages from the cpuset
or the nodes it depends on. This wouldn't be good for NUMA machine
without cpusets either.
Do you have any plans about it?
This patch keeps pdflush daemons on the same cpuset as their
parent, the kthread daemon.
Some large NUMA configurations put as much as they can of
kernel threads and other classic Unix load in what's called a
bootcpuset, keeping the rest of the system free for dedicated
jobs.
This effort is thwarted by pdflush, which dynamically destroys
and recreates pdflush daemons depending on load.
Thanks,parent, the kthread daemon.
Some large NUMA configurations put as much as they can of
kernel threads and other classic Unix load in what's called a
bootcpuset, keeping the rest of the system free for dedicated
jobs.
This effort is thwarted by pdflush, which dynamically destroys
and recreates pdflush daemons depending on load.
Hirokazu Takahashi.