Messages in this thread |  | | Subject | Re: [ANNOUNCE] 3.8-rc6-nohz4 | From | Steven Rostedt <> | Date | Wed, 06 Feb 2013 21:50:15 -0500 |
| |
I'll reply to this as I come up with comments.
First thing is, don't call it NO_HZ_FULL. A better name would be NO_HZ_CPU. I would like to reserve NO_HZ_FULL when we totally remove jiffies :-)
And the kconfig help should probably call it "Adaptive tickless" or "Tickless for single tasks". The full tickless system really sounds like we totally removed jiffies. It should explain it better. Something like:
"Adaptive tickless system"
With this option, you may designate CPUs that will turn off the periodic interrupt "tick" when only a single task is scheduled on the CPU. This is similar to NO_HZ where the tick is suspended when the CPU goes into idle. With this option, it takes it one step further. When only a single task is scheduled on the CPU, there scheduler does not need to keep track of time slices, as the running task does not need to be preempted for other tasks. Stopping the tick allows the task to avoid being interrupted by service routines by the kernel.
CPUs must be designated at time of boot via the kernel command line parameter (cpu_nohz) and must be a subset of the rcu_nocb parameter, which prevents RCU service routines from being called on the CPUs as well.
---
Something like that.
-- Steve
|  |