On 11/29/06, Paul Jackson <[EMAIL PROTECTED]> wrote:
2) I wedged the kernel on the container_lock, doing a removal of a cpuset
using notify_on_release.
I couldn't reproduce this, with a /sbin/cpuset_release_agent that does:
#!/bin/bash
logger cpuset_release_agent $1
rmdir /dev/cpuset/$1
a
On 11/29/06, Paul Jackson <[EMAIL PROTECTED]> wrote:
config PROC_PID_CPUSET
bool "Include legacy /proc//cpuset file"
depends on CPUSETS
+ default y if CPUSETS
Sounds very reasonable.
2) I wedged the kernel on the container_lock, doing a removal of a cpuset
using not
I got a chance to build and test this patch set, to see if it behaved
like I expected cpusets to behave, on an ia64 SN2 Altix system.
Two details - otherwise looked good. I continue to like this
approach.
The two details are (1) /proc//cpuset not configured by
default if CPUSETS configured, and
3 matches
Mail list logo