Hi there.
Just to draw a line under the CPU0 isolation subject. According to RPi kernel development this feature is no longer available. What's happening? At powerup CPU0 starts up first. The rest of the bunch launches a tick later. In between comes the isolcpus function. At that point in time only CPU0 is up. At least one CPU must be available. That's why it won't get isolated. It used to be done this way that the isolcpus function predicted there'd me more CPUs to be launched. And therefore allowed CPU0 isolation. That changed. I also learned that the "isolcpus" boot parameter got the label "depreciated". It seems "cpuset" should be used in the future. isolcpus still works. Enjoy. :::' my blog - latest: \"The Audio Streaming Series\" ' (http://soundcheck-audio.blogspot.com)::: ------------------------------------------------------------------------ soundcheck's Profile: http://forums.slimdevices.com/member.php?userid=34383 View this thread: http://forums.slimdevices.com/showthread.php?t=113512 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
