sched: dynamically adapt granularity with nr_running
Subsystems (3)
cover sched: dynamically adapt granularity with nr_running
Changing the minimum granularity is a double-edged sword: if we set it to a too small value, then the scheduler will preempt tasks too often. If it is too large, then the "latency" period can grow very large as the number of running tasks increases.
The first patch leaves the same scheduling granularity when there are few tasks on the system (3 or less), but dynamically adapts (shrinks) the sched granularity when there are more. At a ceiling value of 8 running tasks (this choice is arbitrary), it grows the latency rather than shrinking granularity further to ensure we don't end up calling the scheduler too often.
The second patch ensures that awakened sleeping tasks don't get affected by shrinked minimum granularity.
Comments are welcome,
Thanks,
Mathieu
Signature · 4 lines
Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
RFC PATCH 1/2 sched: dynamically adapt granularity with nr_running
Changing the minimum granularity is a double-edged sword: if we set it to a too small value, then the scheduler will preempt tasks too often. If it is too large, then the "latency" period can grow very large as the number of running tasks increases.
This patch leaves the same scheduling granularity when there are few tasks on the system (3 or less), but dynamically adapts (shrinks) the sched granularity when there are more. At a ceiling value of 8 running tasks (this choice is arbitrary), it grows the latency rather than shrinking granularity further to ensure we don't end up calling the scheduler too often.
(on a uniprocessor 2.0 GHz Pentium M)
* Without the patch:
- wakeup-latency with SIGEV_THREAD in parallel with youtube video and make -j10
maximum latency: 50107.8 µs
average latency: 6609.2 µs
missed timer events: 0
- wakeup-latency with SIGEV_SIGNAL in parallel with youtube video and make -j10
maximum latency: 8608.3 µs
average latency: 101.3 µs
missed timer events: 0
* With the patch
- wakeup-latency with SIGEV_THREAD in parallel with youtube video and make -j10
maximum latency: 26367.4 µs
average latency: 5382.6 µs
missed timer events: 0
- wakeup-latency with SIGEV_SIGNAL in parallel with youtube video and make -j10
maximum latency: 3030.4 µs
average latency: 129.3 µs
missed timer events: 0
--- kernel/sched_debug.c | 1 + kernel/sched_fair.c | 39 +++++++++++++++++++++++++++++---------- 2 files changed, 30 insertions(+), 10 deletions(-)
kernel/sched_fair.c +29 -10
@@ -51,16 +51,23 @@ enum sched_tunable_scaling sysctl_sched_ = SCHED_TUNABLESCALING_LOG;/* -* Minimal preemption granularity for CPU-bound tasks: +* Minimum preemption granularity (when number of tasks increases). +*/ +unsigned int sysctl_sched_min_granularity =750000ULL ; +unsigned int normalized_sysctl_sched_min_granularity =750000ULL ; + +/* +* Standard preemption granularity for CPU-bound tasks: * (default: 2 msec * (1 + ilog(ncpus)), units: nanoseconds) */ -unsigned int sysctl_sched_min_granularity =2000000ULL ; -unsigned int normalized_sysctl_sched_min_granularity =2000000ULL ; +unsigned int sysctl_sched_std_granularity =2000000ULL ; +unsigned int normalized_sysctl_sched_std_granularity =2000000ULL ;/* -* is kept at sysctl_sched_latency / sysctl_sched_min_granularity +* is kept at sysctl_sched_latency / sysctl_sched_std_granularity */ static unsigned int sched_nr_latency =3 ; +static unsigned int sched_nr_latency_max =8 ;/* * After fork, child runs first. If set to 0 (default) then
@@ -439,24 +446,36 @@ calc_delta_fair(unsigned long delta, str/* * The idea is to set a period in which each task runs once. * -* When there are too many tasks (sysctl_sched_nr_latency) we have to stretch -* this period because otherwise the slices get too small. +* When there are too many tasks (sysctl_sched_nr_latency) we have to shrink the +* slices, up to sysctl_sched_min_granularity. * * p = (nr <= nl) ? l : l*nr/nl */ static u64 __sched_period (unsigned long nr_running) { +unsigned long nr_latency_max = sched_nr_latency_max;u64 period = sysctl_sched_latency; -unsigned long nr_latency = sched_nr_latency; -if (unlikely (nr_running > nr_latency)) { +if (unlikely (nr_running > nr_latency_max)) { period = sysctl_sched_min_granularity; period *= nr_running; } -return period; } +static unsigned int __sched_gran (unsigned long nr_running) +{ +unsigned int gran = sysctl_sched_std_granularity; +unsigned long nr_latency = sched_nr_latency; + +if (unlikely (nr_running > nr_latency)) { + gran = sysctl_sched_latency; + gran /= nr_running; + gran =max (gran, sysctl_sched_min_granularity); + } +return gran; +} +/* * We calculate the wall-time slice from the period by taking a part * proportional to the weight.
@@ -862,7 +881,7 @@ check_preempt_tick(struct cfs_rq *cfs_rqif (!sched_feat (WAKEUP_PREEMPT ))return ; -if (delta_exec < sysctl_sched_min_granularity) +if (delta_exec <__sched_gran (cfs_rq->nr_running))return ;if (cfs_rq->nr_running >1 ) {
kernel/sched_debug.c +1 -0
@@ -331,6 +331,7 @@ static int sched_debug_show(struct seq_fP (jiffies);PN (sysctl_sched_latency);PN (sysctl_sched_min_granularity); +PN (sysctl_sched_std_granularity);PN (sysctl_sched_wakeup_granularity);PN (sysctl_sched_child_runs_first);P (sysctl_sched_features);
Peter Zijlstra
maintainerOn Sat, 2010-09-11 at 13:37 -0400, Mathieu Desnoyers wrote:
Its not at all clear what or why you're doing what exactly.
What we used to have is:
period -- time in which each task gets scheduled once
This period was adaptive in that we had an ideal period (sysctl_sched_latency), but since keeping to this means that each task gets latency/nr_running time. This is undesired in that it means busy systems will over-schedule due to tiny slices. Hence we also had a minimum slice (sysctl_sched_min_granularity).
This yields:
period := max(sched_latency, nr_running * sched_min_granularity)
[ where we introduce the intermediate:
nr_latency := sched_latency / sched_min_granularity
in order to avoid the multiplication where possible ]
Now you introduce a separate preemption measure, sched_gran as:
sched_std_granularity; nr_running <= 8
sched_gran := {
max(sched_min_granularity, sched_latency / nr_running)
Which doesn't make any sense at all, because it will either be larger or as large as the current sched_min_granularity.
And you break the above definition of period by replacing nr_latency by 8.
Not at all charmed, this look like random changes without conceptual integrity.
Quoted 3 lines · Peter Zijlstra
Not at all charmed, this look like random changes without conceptual integrity.
I wish people actually looked at the _numbers_ and reacted to them, rather than argue theory.
Guys, we have cases of bad latency under load. That's a pretty undeniable fact. Arguing against a patch because of some theoretical issue without at all even acknowledging the latency improvements is, I think, really bad form.
So please. Acknowledge the latency issue. And come up with better patches, rather than just shoot down alternatives. Because if the answer is just NAK with no alternative, then that answer is worthless. No?
Linus
Peter Zijlstra
maintainerQuoted 13 lines · Linus Torvalds
Quoted 3 lines · Peter Zijlstra
Not at all charmed, this look like random changes without conceptual integrity.
I wish people actually looked at the _numbers_ and reacted to them, rather than argue theory.
Guys, we have cases of bad latency under load. That's a pretty undeniable fact. Arguing against a patch because of some theoretical issue without at all even acknowledging the latency improvements is, I think, really bad form.
Quoted 6 lines
So please. Acknowledge the latency issue. And come up with better patches, rather than just shoot down alternatives. Because if the answer is just NAK with no alternative, then that answer is worthless. No?
From what I can make up:
LAT=`cat /proc/sys/kernel/sched_latency_ns`; echo $((LAT/8)) > /proc/sys/kernel/sched_min_granularity_ns
will give you pretty much the same result as Mathieu's patch.
But if you want us to change the scheduler to be more latency sensitive and trade in throughput for other benchmarks, we can do that.
Peter Zijlstra
maintainerQuoted 3 lines · Peter Zijlstra
But if you want us to change the scheduler to be more latency sensitive and trade in throughput for other benchmarks, we can do that.
Really, just say "latency trumps throughput" and we'll make it so.
Quoted 6 lines · Peter Zijlstra
Quoted 3 lines · Peter Zijlstra
But if you want us to change the scheduler to be more latency sensitive and trade in throughput for other benchmarks, we can do that.
Really, just say "latency trumps throughput" and we'll make it so.
Nothing is ever that black-and-white.
But latency really _is_ important. And it's often overlooked, because few benchmarks actually test it. So when somebody sends you actual measured latency numbers, you shouldn't be so cavalier. And you shouldn't say "trumps throughput", since it's clearly a matter of balancing, and quite frankly, Mathieu's patch does seem to try to balance things.
As mentioned, it does seem to make tons of conceptual sense to take the number of running threads into account for the whole scheduling granularity decision. After all, we already do that for the other important numbers (the scheduling period and time slice).
So to me it looks like you're just being negative, without actually looking at the patch and giving it some fair thought. That's what I'm objecting to.
Linus
Peter Zijlstra
maintainerQuoted 3 lines · Linus Torvalds
So to me it looks like you're just being negative, without actually looking at the patch and giving it some fair thought. That's what I'm objecting to.
I hope my reply just now cleared that up.
Quoted 7 lines · Peter Zijlstra
From what I can make up:
LAT=
cat /proc/sys/kernel/sched_latency_ns;
echo $((LAT/8)) >/proc/sys/kernel/sched_min_granularity_nswill give you pretty much the same result as Mathieu's patch.
Or perhaps not. The point being that Mathieu's patch seems to do this dynamically based on number of runnable threads per cpu. Which seems to be a good idea.
IOW, this part:
- if (delta_exec < sysctl_sched_min_granularity)
+ if (delta_exec < __sched_gran(cfs_rq->nr_running))
seems to be a rather fundamental change, and looks at least potentially interesting. It seems to make conceptual sense to take the number of running tasks into account at that point, no?
And I don't like how you dismissed the measured latency improvement. And yes, I do think latency matters. A _lot_.
And no, I'm not saying that Mathieu's patch is necessarily good. I haven't tried it myself. I don't have _that_ kind of opinion. The opinion I do have is that I think it's sad how you dismissed things out of hand - and seem to _continue_ to dismiss them without apparently actually having looked at the patch at all.
Linus
Peter Zijlstra
maintainerQuoted 18 lines · Linus Torvalds
Quoted 7 lines · Peter Zijlstra
From what I can make up:
LAT=
cat /proc/sys/kernel/sched_latency_ns;
echo $((LAT/8)) >/proc/sys/kernel/sched_min_granularity_nswill give you pretty much the same result as Mathieu's patch.
Or perhaps not. The point being that Mathieu's patch seems to do this dynamically based on number of runnable threads per cpu. Which seems to be a good idea.
IOW, this part:
kernel/sched_fair.c +1
-1-if (delta_exec < sysctl_sched_min_granularity) +if (delta_exec <__sched_gran (cfs_rq->nr_running))
Quoted 3 lines
seems to be a rather fundamental change, and looks at least potentially interesting. It seems to make conceptual sense to take the number of running tasks into account at that point, no?
We used to have something like that a long while back, we nixed it because of the division and replaced it with floor(__sched_gran) (ie. the smallest value it would ever give).
Smaller values are better for latency, larger values are better for throughput. So introducing __sched_gran() in order to provide larger values doesn't make sense to me.
Quoted 2 lines
And I don't like how you dismissed the measured latency improvement. And yes, I do think latency matters. A _lot_.
OK, we'll make it better and sacrifice some throughput, can do, no problem.
Quoted 5 lines
And no, I'm not saying that Mathieu's patch is necessarily good. I haven't tried it myself. I don't have _that_ kind of opinion. The opinion I do have is that I think it's sad how you dismissed things out of hand - and seem to _continue_ to dismiss them without apparently actually having looked at the patch at all.
Let me draw you a picture of what this patch looks like to me:
* is slice length, + is period length
Patch (sched_latency = 10, sched_min_gran = 10/3)
30 | + | | | + | | | | | | 20 | | | | | | | | | | 10 | * + + + + + + + | | | | | * | | * * * * * * * * | * * | * * 0 +---------------------------------------------------------
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Normal (sched_latency = 10, sched_min_gran = 10/3)
30 | +
|
|
| +
|
|
|
| +
|
|
20 | +
|
|
| +
|
|
|
| +
|
|
10 | * + +
|
|
|
|
| *
|
| * * * * * * * * * * * * * *
|
|
0 +---------------------------------------------------------
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16Normal (sched_latency = 10, sched_min_gran = 10/8)
30 | | | | | | | | | | 20 | | | | | | + | + | + | | + 10 | * + + + + + + + | | | | | * | | * * | * * | * * * * * * * * 0 +---------------------------------------------------------
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Peter Zijlstra
maintainerQuoted 36 lines · Peter Zijlstra
* is slice length, + is period length
Patch (
sched_latency= 10,sched_min_gran= 10/3)30 | + | | | + | | | | | | 20 | | | | | | | | | | 10 | * + + + + + + + | | | | | * | | * * * * * * * * | * * | * * 0 +---------------------------------------------------------
Quoted 1 line
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Vertical is time , horz is nr_running.
Note how things fall of a cliff when nr_running goes from 8 to 9. Andrew usually kicks people in the teeth for phase change behaviour.
Quoted 40 lines · * Peter Zijlstra ([email protected]) wrote:
Quoted 36 lines · Peter Zijlstra
* is slice length, + is period length
Patch (
sched_latency= 10,sched_min_gran= 10/3)30 | + | | | + | | | | | | 20 | | | | | | | | | | 10 | * + + + + + + + | | | | | * | | * * * * * * * * | * * | * * 0 +---------------------------------------------------------Quoted 1 line
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Quoted 5 lines
Vertical is time , horz is
nr_running.Note how things fall of a cliff when
nr_runninggoes from 8 to 9. Andrew usually kicks people in the teeth for phase change behaviour.
Please refer to my other email asking why your sched_latency = 10 rather than what I see in sched_fair.c:
unsigned int sysctl_sched_latency = 6000000ULL;
I really might have missed something important there. Is this value recomputed dynamically somewhere ?
Thanks,
Mathieu
Signature · 4 lines
Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
Peter Zijlstra
maintainerQuoted 3 lines · Mathieu Desnoyers
I really might have missed something important there. Is this value recomputed dynamically somewhere ?
People can set it using sysctl (and people do).
I simply used 10 because it was easier to draw graphs from.
Quoted 23 lines · * Peter Zijlstra ([email protected]) wrote:
Quoted 18 lines · Linus Torvalds
Quoted 7 lines · Peter Zijlstra
From what I can make up:
LAT=
cat /proc/sys/kernel/sched_latency_ns;
echo $((LAT/8)) >/proc/sys/kernel/sched_min_granularity_nswill give you pretty much the same result as Mathieu's patch.
Or perhaps not. The point being that Mathieu's patch seems to do this dynamically based on number of runnable threads per cpu. Which seems to be a good idea.
IOW, this part:
kernel/sched_fair.c +1
-1-if (delta_exec < sysctl_sched_min_granularity) +if (delta_exec <__sched_gran (cfs_rq->nr_running))Quoted 3 lines
seems to be a rather fundamental change, and looks at least potentially interesting. It seems to make conceptual sense to take the number of running tasks into account at that point, no?
Quoted 7 lines
We used to have something like that a long while back, we nixed it because of the division and replaced it with
floor(__sched_gran)(ie. the smallest value it would ever give).Smaller values are better for latency, larger values are better for throughput. So introducing
__sched_gran()in order to provide larger values doesn't make sense to me.
__sched_gran() provides large values for small nr_running, and smaller values for larger nr_running.
So for systems with few threads running, we have good throughput (and there does not seem to be much latency issues there). However for a system with a larger number of running threads, __sched_gran() dynamically reduces the granularity.
Quoted 6 lines
Quoted 3 lines
And I don't like how you dismissed the measured latency improvement. And yes, I do think latency matters. A _lot_.
OK, we'll make it better and sacrifice some throughput, can do, no problem.
My approach try to get lower latencies without sacrificing throughput when there are few threads running, which IMHO is the common case where throughput really matters. A system running tons of threads should already expect some sort of throughput degradation anyway, so we might as well favor low-latency rather than throughput on those systems running lots of threads.
Quoted 7 lines
Quoted 6 lines
And no, I'm not saying that Mathieu's patch is necessarily good. I haven't tried it myself. I don't have _that_ kind of opinion. The opinion I do have is that I think it's sad how you dismissed things out of hand - and seem to _continue_ to dismiss them without apparently actually having looked at the patch at all.
Quoted 5 lines
Let me draw you a picture of what this patch looks like to me:
* is slice length, + is period length
Patch (
sched_latency= 10,sched_min_gran= 10/3)
Hrm, in sched_fair.c, sysctl_sched_latency is set to 6000000ULL. So this would be a sched_latency = 6, or am I missing something ? With a sched_latency of 6, the jump you show below in your graph disappears. So what have I missed ?
I agree with the shape of your graph, I'm just trying to understand why you have a sched_latency of 10.
Thanks,
Mathieu
Quoted 119 lines
30 | + | | | + | | | | | | 20 | | | | | | | | | | 10 | * + + + + + + + | | | | | * | | * * * * * * * * | * * | * * 0 +---------------------------------------------------------0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Normal (
sched_latency= 10,sched_min_gran= 10/3)30 | + | | | + | | | | + | | 20 | + | | | + | | | | + | | 10 | * + + | | | | | * | | * * * * * * * * * * * * * * | | 0 +--------------------------------------------------------- 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16Normal (
sched_latency= 10,sched_min_gran= 10/8)30 | | | | | | | | | | 20 | | | | | | + | + | + | | + 10 | * + + + + + + + | | | | | * | | * * | * * | * * * * * * * * 0 +---------------------------------------------------------0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Signature · 4 lines
Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
Peter Zijlstra
maintainerQuoted 2 lines · Mathieu Desnoyers
I agree with the shape of your graph, I'm just trying to understand why you have a
sched_latencyof 10.
Was easier to draw the graph :-)
Quoted 7 lines · Peter Zijlstra
Quoted 2 lines · Linus Torvalds
And I don't like how you dismissed the measured latency improvement. And yes, I do think latency matters. A _lot_.
OK, we'll make it better and sacrifice some throughput, can do, no problem.
I'm not seeing high wakeup latencies, even under hefty load. Mathieu's testcase is bad, but apparently solely due to START_DEBIT placement. That's kind of a sticky wicket. I've shot it in the heart before, but regretted doing so when I looked at kbuild vs static load fairness.
-Mike
Peter Zijlstra
maintainerQuoted 6 lines · Mike Galbraith
Quoted 5 lines · Peter Zijlstra
Quoted 2 lines · Linus Torvalds
And I don't like how you dismissed the measured latency improvement. And yes, I do think latency matters. A _lot_.
Quoted 7 lines
Quoted 2 lines
OK, we'll make it better and sacrifice some throughput, can do, no problem.
I'm not seeing high wakeup latencies, even under hefty load. Mathieu's testcase is bad, but apparently solely due to
START_DEBITplacement. That's kind of a sticky wicket. I've shot it in the heart before, but regretted doing so when I looked at kbuild vs static load fairness.
Yeah, without it you can starve the already running task on massive forks.
Still, I'm not quite sure why people really care about fork() on time sensitive paths, its a very expensive thing to do, pre-fork() and wake when you need it, is what I would say.
Quoted 16 lines · Peter Zijlstra
Quoted 6 lines · Mike Galbraith
Quoted 5 lines · Peter Zijlstra
Quoted 2 lines · Linus Torvalds
And I don't like how you dismissed the measured latency improvement. And yes, I do think latency matters. A _lot_.
Quoted 8 lines
Quoted 2 lines
OK, we'll make it better and sacrifice some throughput, can do, no problem.
I'm not seeing high wakeup latencies, even under hefty load. Mathieu's testcase is bad, but apparently solely due to
START_DEBITplacement. That's kind of a sticky wicket. I've shot it in the heart before, but regretted doing so when I looked at kbuild vs static load fairness.
Quoted 6 lines
Yeah, without it you can starve the already running task on massive forks.
Still, I'm not quite sure why people really care about
fork()on time sensitive paths, its a very expensive thing to do, pre-fork() and wake when you need it, is what I would say.
Right. So what happens in practice is that some desktop apps tend to be fork happy and it doesnt show up on low load so why not? The kernel forks plenty fast:
aldebaran:~/l> ./lat_proc fork
Process fork+exit: 165.9254 microseconds
So even a full-blown fork() is a drop in the ocean of desktop bloat. Firefox takes 100-300 msecs CPU time to process a single tab click ... it's insane.
fork() is also a very convenient and robust prgramming facility: COW gives us immutable data inheritance - match that thread programmers ...
Plus it's not just fork()s but also pthread_create() obviously - which is even faster.
So yes, it happens all the time, and if we create some bad latency of 10-20 msecs under load (or more), it gets noticed - especially if it's some cumulative fork() chain of processing.
And no, we cannot rely on pre-forking - and we dont even _want_ to, fork() and pthread_create() is a perfectly valid facility. In the scheduler we have to handle fork()/pthread_create() smoothly.
Thanks,
Ingo
Steven Rostedt
reviewerQuoted 6 lines · Peter Zijlstra
Yeah, without it you can starve the already running task on massive forks.
Still, I'm not quite sure why people really care about
fork()on time sensitive paths, its a very expensive thing to do, pre-fork() and wake when you need it, is what I would say.
Fork is used all over the place in Linux. Every shell script uses it to execute commands. Bad fork behavior shows up in just doing a build of the kernel.
-- Steve
Peter Zijlstra
maintainerQuoted 5 lines · Steven Rostedt
Quoted 3 lines · Peter Zijlstra
Yeah, without it you can starve the already running task on massive forks.
Quoted 7 lines
Quoted 3 lines
Still, I'm not quite sure why people really care about
fork()on time sensitive paths, its a very expensive thing to do, pre-fork() and wake when you need it, is what I would say.Fork is used all over the place in Linux. Every shell script uses it to execute commands. Bad fork behavior shows up in just doing a build of the kernel.
Sure, but there's a difference between bad fork behaviour and the lowest possible latency. But maybe I'm too paranoid from doing -rt, but the first thing I'd do is get all resource allocations out from your fast path.
Peter Zijlstra
maintainerQuoted 10 lines · Peter Zijlstra
Quoted 9 lines · Steven Rostedt
Quoted 6 lines · Peter Zijlstra
Yeah, without it you can starve the already running task on massive forks.
Still, I'm not quite sure why people really care about
fork()on time sensitive paths, its a very expensive thing to do, pre-fork() and wake when you need it, is what I would say.
Quoted 8 lines
Quoted 3 lines
Fork is used all over the place in Linux. Every shell script uses it to execute commands. Bad fork behavior shows up in just doing a build of the kernel.
Sure, but there's a difference between bad fork behaviour and the lowest possible latency. But maybe I'm too paranoid from doing -rt, but the first thing I'd do is get all resource allocations out from your fast path.
That is, with fork there's a trace-off between disrupting existing tasks and their expectations, and running the new child.
There's also the issue that letting the parent run a little longer could result in more runnable children, yielding greater parallelism.
If you push the new child all the way to the front, tasks that prefer the parent to run a little more will suck, and vs.
IIRC kbuild likes the child to be late, it allows make to spawn more kids and it'll got sleep on completion once it done anyway.
Quoted 2 lines · Peter Zijlstra
IIRC kbuild likes the child to be late, it allows make to spawn more kids and it'll got sleep on completion once it done anyway.
Yes - and this is especially true on "make -j<nr_cpus>" types of borderline workloads - the scheduling policy with the highest effective parallelism wins.
Thanks,
Ingo
Quoted 19 lines · * Peter Zijlstra ([email protected]) wrote:
Quoted 17 lines · Linus Torvalds
Quoted 3 lines · Peter Zijlstra
Not at all charmed, this look like random changes without conceptual integrity.
I wish people actually looked at the _numbers_ and reacted to them, rather than argue theory.
Guys, we have cases of bad latency under load. That's a pretty undeniable fact. Arguing against a patch because of some theoretical issue without at all even acknowledging the latency improvements is, I think, really bad form.
So please. Acknowledge the latency issue. And come up with better patches, rather than just shoot down alternatives. Because if the answer is just NAK with no alternative, then that answer is worthless. No?
Quoted 6 lines
Quoted 1 line
From what I can make up:
LAT=`cat /proc/sys/kernel/sched_latency_ns`; echo $((LAT/8)) > /proc/sys/kernel/sched_min_granularity_nswill give you pretty much the same result as Mathieu's patch.
Not quite. Doing what you propose here would change the scheduling granularity (thus decrease throughput because it would schedule more often) when there are few tasks running. My approach does not: it only shrinks granularity when the number of running tasks increases over 3.
Thanks,
Mathieu
Quoted 3 lines
But if you want us to change the scheduler to be more latency sensitive and trade in throughput for other benchmarks, we can do that.
Signature · 4 lines
Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
Quoted 28 lines · * Peter Zijlstra ([email protected]) wrote:
On Sat, 2010-09-11 at 13:37 -0400, Mathieu Desnoyers wrote:
Its not at all clear what or why you're doing what exactly.
What we used to have is:
period -- time in which each task gets scheduled once
This period was adaptive in that we had an ideal period (
sysctl_sched_latency), but since keeping to this means that each task gets latency/nr_running time. This is undesired in that it means busy systems will over-schedule due to tiny slices. Hence we also had a minimum slice (sysctl_sched_min_granularity).This yields:
period :=
max(sched_latency, nr_running * sched_min_granularity)[ where we introduce the intermediate:
nr_latency:=sched_latency/sched_min_granularity
in order to avoid the multiplication where possible ]Now you introduce a separate preemption measure,
sched_granas:
sched_std_granularity;nr_running<= 8
sched_gran:= {
max(sched_min_granularity, sched_latency / nr_running)
Quoted 8 lines
Which doesn't make any sense at all, because it will either be larger or as large as the current
sched_min_granularity.And you break the above definition of period by replacing
nr_latencyby 8.Not at all charmed, this look like random changes without conceptual integrity.
Err.. I think the preemption measure you are describing does not match my code, so let's try to figure this one out. Here is what I am doing:
nr_latency is still 3.
I introduce nr_latency_max (8).
sched_min_granularity is now sched_latency / nr_latency_max sched_std_granularity is sched_latency / nr_latency
sched_std_granularity is the granularity effective when there are 3 tasks or less running. This is the exact same behavior as the current kernel.
For more than 8 tasks, the behavior is the same as the current kernel (we increase the scheduling period, ergo the latency); we are using the new "sched_min_granularity" (which is now sched_latency / 8 rather than sched_latency /3).
The interesting part is in the range from 4 to 8 tasks. I diminish the scheduler granularity as the number of tasks increases rather than increasing latency. This leads to more scheduler preemptions than usual, but only in the 4-8 running tasks range.
We could possibly fine-tune nr_latency_max to a value that would keep an appropriate sched_min_granularity (that would not cause an insane rate of scheduler events).
The major interest in the approach I propose (rather than just increasing nr_latency and decreasing sched_min_granularity) is that I don't have to change the scheduler granularity when there are only few tasks running. So the extra scheduler overhead is only taken when we are running more tasks.
I hope my explanation clarifies things a bit,
Thanks,
Mathieu
Signature · 4 lines
Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
Peter Zijlstra
maintainerQuoted 4 lines · Mathieu Desnoyers
The interesting part is in the range from 4 to 8 tasks. I diminish the scheduler granularity as the number of tasks increases rather than increasing latency. This leads to more scheduler preemptions than usual, but only in the 4-8 running tasks range.
I really don't get it.. that's exactly what it does from the 1..3 range too, if you want to extend that, simply set a lower min_gran, it will update nr_latency and you get it from 1..(latency/min_gran) range.
And you didn't touch sched_proc_update_handler(), which recomputes sched_nr_latency when you change sched_latency or sched_min_gran.
So the current stuff is:
period := max(latency, min_gran * nr_running)
or, conversely:
gran := max(min_gran, latency / nr_running)
Which seems to be exactly what you want, no? Its doing that!
Except that in the one place we used 'gran' directly we avoided the division and used the minimal value: min_gran in all cases, which is a trade-of favouring latency.
Quoted 19 lines · * Peter Zijlstra ([email protected]) wrote:
Quoted 4 lines · Mathieu Desnoyers
The interesting part is in the range from 4 to 8 tasks. I diminish the scheduler granularity as the number of tasks increases rather than increasing latency. This leads to more scheduler preemptions than usual, but only in the 4-8 running tasks range.
I really don't get it.. that's exactly what it does from the 1..3 range too, if you want to extend that, simply set a lower
min_gran, it will updatenr_latencyand you get it from 1..(latency/min_gran) range.And you didn't touch
sched_proc_update_handler(), which recomputessched_nr_latencywhen you changesched_latencyorsched_min_gran.So the current stuff is:
period :=
max(latency, min_gran * nr_running)or, conversely:
Quoted 7 lines
gran :=
max(min_gran, latency / nr_running)Which seems to be exactly what you want, no? Its doing that!
Except that in the one place we used 'gran' directly we avoided the division and used the minimal value:
min_granin all cases, which is a trade-of favouring latency.
The whole point of my patch is not to have to do this latency vs performance tradeoff for low number of running threads. With your approach, lowering the granularity even when there are few threads running will very likely hurt performance, no ?
Mathieu
Signature · 4 lines
Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
Peter Zijlstra
maintainerQuoted 4 lines · Mathieu Desnoyers
The whole point of my patch is not to have to do this latency vs performance tradeoff for low number of running threads. With your approach, lowering the granularity even when there are few threads running will very likely hurt performance, no ?
But you presented it as a latency patch, not a throughput patch. And I'm not sure it will matter enough to offset the computational cost it introduces.
Peter Zijlstra
maintainerQuoted 9 lines · Peter Zijlstra
Quoted 4 lines · Mathieu Desnoyers
The whole point of my patch is not to have to do this latency vs performance tradeoff for low number of running threads. With your approach, lowering the granularity even when there are few threads running will very likely hurt performance, no ?
But you presented it as a latency patch, not a throughput patch. And I'm not sure it will matter enough to offset the computational cost it introduces.
---
On Mon, 2010-09-13 at 14:53 +0200, Peter Zijlstra wrote:
Quoted 9 lines · Mathieu Desnoyers
Quoted 4 lines
The whole point of my patch is not to have to do this latency vs performance tradeoff for low number of running threads. With your approach, lowering the granularity even when there are few threads running will very likely hurt performance, no ?
But you presented it as a latency patch, not a throughput patch. And I'm not sure it will matter enough to offset the computational cost it introduces.
One option is to simply get rid of that stuff in check_preempt_tick() and instead do a wakeup-preempt check on the leftmost task instead.
The code as it stands today does that delta_exec < min_gran check to ensure current gets some runtime before doing that second preemption check, which compares vruntime with a wall-time measure.
Making that gran more complex doesn't really buy us much because for a system with different weights in the gran and slice lengths don't match up anyway.
---
Subject: sched: Simplify tick preemption
From: Peter Zijlstra <[email protected]>
Date: Mon Jul 05 13:56:30 CEST 2010
Check the current slice, if not expired, see if the leftmost task would otherwise have preempted current.
--- kernel/sched_fair.c | 43 +++++++++++++++---------------------------- 1 file changed, 15 insertions(+), 28 deletions(-)
kernel/sched_fair.c +15 -28
@@ -838,44 +838,34 @@ dequeue_entity(struct cfs_rq *cfs_rq, st se->vruntime -= cfs_rq->min_vruntime; } +static int +wakeup_preempt_entity (struct sched_entity *curr,struct sched_entity *se); +/* * Preempt the current task with a newly woken task if needed: */ static void check_preempt_tick (struct cfs_rq *cfs_rq,struct sched_entity *curr) { -unsigned long ideal_runtime, delta_exec; +unsigned long slice =sched_slice (cfs_rq, curr); + +if (curr->sum_exec_runtime - curr->prev_sum_exec_runtime < slice) { +struct sched_entity *pse =__pick_next_entity (cfs_rq); + +if (pse &&wakeup_preempt_entity (curr, pse) ==1 ) + goto preempt; - ideal_runtime =sched_slice (cfs_rq, curr); - delta_exec = curr->sum_exec_runtime - curr->prev_sum_exec_runtime; -if (delta_exec > ideal_runtime) { -resched_task (rq_of (cfs_rq)->curr); -/* -* The current task ran long enough, ensure it doesn't get -* re-elected due to buddy favours. -*/ -clear_buddies (cfs_rq, curr);return ; }/* -* Ensure that a task that missed wakeup preemption by a -* narrow margin doesn't have to wait for a full slice. -* This also mitigates buddy induced latencies under load. +* The current task ran long enough, ensure it doesn't get +* re-elected due to buddy favours. */ -if (!sched_feat (WAKEUP_PREEMPT )) -return ; - -if (delta_exec < sysctl_sched_min_granularity) -return ; +clear_buddies (cfs_rq, curr); -if (cfs_rq->nr_running >1 ) { -struct sched_entity *se =__pick_next_entity (cfs_rq); -s64 delta = curr->vruntime - se->vruntime; - -if (delta > ideal_runtime) -resched_task (rq_of (cfs_rq)->curr); - } +preempt: +resched_task (rq_of (cfs_rq)->curr); } static void
@@ -908,9 +898,6 @@ set_next_entity(struct cfs_rq *cfs_rq, s se->prev_sum_exec_runtime = se->sum_exec_runtime; } -static int -wakeup_preempt_entity (struct sched_entity *curr,struct sched_entity *se); -static struct sched_entity *pick_next_entity (struct cfs_rq *cfs_rq) {struct sched_entity *se =__pick_next_entity (cfs_rq);
Quoted 10 lines · * Peter Zijlstra ([email protected]) wrote:
Quoted 9 lines · Peter Zijlstra
Quoted 4 lines · Mathieu Desnoyers
The whole point of my patch is not to have to do this latency vs performance tradeoff for low number of running threads. With your approach, lowering the granularity even when there are few threads running will very likely hurt performance, no ?
But you presented it as a latency patch, not a throughput patch. And I'm not sure it will matter enough to offset the computational cost it introduces.
Can we agree that the patch I proposed is a patch that try to improve _latency_ under high load while preserving good throughput under lower load ? I find this "performance" XOR "latency" dichotomy itching: it's like looking at an american TV show where all bad guys are dressed in black, and the hero is in white.
Quoted 18 lines
---
On Mon, 2010-09-13 at 14:53 +0200, Peter Zijlstra wrote:Quoted 9 lines · Mathieu Desnoyers
Quoted 4 lines
The whole point of my patch is not to have to do this latency vs performance tradeoff for low number of running threads. With your approach, lowering the granularity even when there are few threads running will very likely hurt performance, no ?
But you presented it as a latency patch, not a throughput patch. And I'm not sure it will matter enough to offset the computational cost it introduces.
One option is to simply get rid of that stuff in
check_preempt_tick()and instead do a wakeup-preempt check on the leftmost task instead.
Quoted 7 lines
The code as it stands today does that
delta_exec<min_grancheck to ensure current gets some runtime before doing that second preemption check, which compares vruntime with a wall-time measure.Making that gran more complex doesn't really buy us much because for a system with different weights in the gran and slice lengths don't match up anyway.
So I bet this last sentence is about the example of a system with many nice 19 processes I told you about on IRC. Yes, this one is a bummer, as we would not like to count them as running threads at all.
More comments below,
Quoted 23 lines
---
Subject: sched: Simplify tick preemption
From: Peter Zijlstra <[email protected]>
Date: Mon Jul 05 13:56:30 CEST 2010Check the current slice, if not expired, see if the leftmost task would otherwise have preempted current.
Signed-off-by Peter Zijlstra <[email protected]>--- kernel/sched_fair.c | 43 +++++++++++++++---------------------------- 1 file changed, 15 insertions(+), 28 deletions(-)Index:
linux-2.6/kernel/sched_fair.c
===================================================================kernel/sched_fair.c +1
-0@@ -838,44 +838,34 @@ dequeue_entity(struct cfs_rq *cfs_rq, st se->vruntime -= cfs_rq->min_vruntime; } +static int
kernel/sched_fair.c dequeue_entity(struct cfs_rq *cfs_rq, st · line 850
Quoted 10 lines
kernel/sched_fair.c +3
-1+wakeup_preempt_entity(struct sched_entity *curr, struct sched_entity *se); +/* * Preempt the current task with a newly woken task if needed: */ static void check_preempt_tick (struct cfs_rq *cfs_rq,struct sched_entity *curr) { -unsigned long ideal_runtime, delta_exec; +unsigned long slice =sched_slice (cfs_rq, curr);
So you still compute the sched_slice(), based on sched_period(), based on sysctl_sched_min_granularity *= nr_running when there are more than nr_latency running threads.
Quoted 21 lines
kernel/sched_fair.c +6
-10+ +if (curr->sum_exec_runtime - curr->prev_sum_exec_runtime < slice) { +struct sched_entity *pse =__pick_next_entity (cfs_rq); + +if (pse &&wakeup_preempt_entity (curr, pse) ==1 ) + goto preempt; - ideal_runtime =sched_slice (cfs_rq, curr); - delta_exec = curr->sum_exec_runtime - curr->prev_sum_exec_runtime; -if (delta_exec > ideal_runtime) { -resched_task (rq_of (cfs_rq)->curr); -/* -* The current task ran long enough, ensure it doesn't get -* re-elected due to buddy favours. -*/ -clear_buddies (cfs_rq, curr);return ; }/* -* Ensure that a task that missed wakeup preemption by a
kernel/sched_fair.c dequeue_entity(struct cfs_rq *cfs_rq, st · line 870
Quoted 10 lines
kernel/sched_fair.c +2
-7-* narrow margin doesn't have to wait for a full slice. -* This also mitigates buddy induced latencies under load. +* The current task ran long enough, ensure it doesn't get +* re-elected due to buddy favours. */ -if (!sched_feat (WAKEUP_PREEMPT )) -return ; - -if (delta_exec < sysctl_sched_min_granularity) -return ;
Well, the reason why this test is here seems to be that we don't want to trigger "resched_task" more often than needed, and here it's defined by the granularity. I don't quite see with what you are replacing this, other than "let's set the resched flag all the time to save a 32-bit division". I figure out it's more expensive the call the scheduler than to do a 32-bit div.
Thanks,
Mathieu
Quoted 25 lines
kernel/sched_fair.c +3
-10+clear_buddies (cfs_rq, curr); -if (cfs_rq->nr_running >1 ) { -struct sched_entity *se =__pick_next_entity (cfs_rq); -s64 delta = curr->vruntime - se->vruntime; - -if (delta > ideal_runtime) -resched_task (rq_of (cfs_rq)->curr); - } +preempt: +resched_task (rq_of (cfs_rq)->curr); } static void@@ -908,9 +898,6 @@ set_next_entity(struct cfs_rq *cfs_rq, s se->prev_sum_exec_runtime = se->sum_exec_runtime; } -static int -wakeup_preempt_entity (struct sched_entity *curr,struct sched_entity *se); -static struct sched_entity *pick_next_entity (struct cfs_rq *cfs_rq) {struct sched_entity *se =__pick_next_entity (cfs_rq);
Signature · 4 lines
Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
Peter Zijlstra
maintainerQuoted 8 lines · Mathieu Desnoyers
Quoted 8 lines
One option is to simply get rid of that stuff in
check_preempt_tick()and instead do a wakeup-preempt check on the leftmost task instead.The code as it stands today does that
delta_exec<min_grancheck to ensure current gets some runtime before doing that second preemption check, which compares vruntime with a wall-time measure.
Quoted 7 lines
Quoted 3 lines
Making that gran more complex doesn't really buy us much because for a system with different weights in the gran and slice lengths don't match up anyway.
So I bet this last sentence is about the example of a system with many nice 19 processes I told you about on IRC. Yes, this one is a bummer, as we would not like to count them as running threads at all.
Of course we would. But the same is true for -5 and 5 threads together.
Quoted 9 lines
kernel/sched_fair.c dequeue_entity(struct cfs_rq *cfs_rq, st · line 850
Quoted 5 lines
static void
check_preempt_tick(struct cfs_rq *cfs_rq, struct sched_entity *curr){kernel/sched_fair.c +1
-1-unsigned long ideal_runtime, delta_exec; +unsigned long slice =sched_slice (cfs_rq, curr);So you still compute the
sched_slice(), based onsched_period(), based onsysctl_sched_min_granularity*=nr_runningwhen there are more thannr_latencyrunning threads.
What's wrong with that? I keep asking you, you keep not giving an answer. Stop focussing on nr_latency, its an by produce not a fundamental entity.
period := max(latency, min_gran * nr_running)
See, no nr_latency -- the one and only purpose of nr_latency is avoiding that multiplication when possible.
Quoted 5 lines
kernel/sched_fair.c dequeue_entity(struct cfs_rq *cfs_rq, st · line 870
Quoted 2 lines
kernel/sched_fair.c +0
-2-if (delta_exec < sysctl_sched_min_granularity) -return ;Well, the reason why this test is here seems to be that we don't want to trigger "
resched_task" more often than needed, and here it's defined by the granularity.
Right, but its wrong for the weighted case. Letting a light task run that long will make its latency suck.
Quoted 3 lines
I don't quite see with what you are replacing this, other than "let's set the resched flag all the time to save a 32-bit division". I figure out it's more expensive the call the scheduler than to do a 32-bit div.
The more divs we put it, the more expensive it all becomes.
Steven Rostedt
reviewerQuoted 6 lines · Peter Zijlstra
Quoted 5 lines
kernel/sched_fair.c dequeue_entity(struct cfs_rq *cfs_rq, st · line 870
Quoted 2 lines
kernel/sched_fair.c +0
-2-if (delta_exec < sysctl_sched_min_granularity) -return ;Well, the reason why this test is here seems to be that we don't want to trigger "
resched_task" more often than needed, and here it's defined by the granularity.
Quoted 9 lines
Right, but its wrong for the weighted case. Letting a light task run that long will make its latency suck.
Quoted 3 lines
I don't quite see with what you are replacing this, other than "let's set the resched flag all the time to save a 32-bit division". I figure out it's more expensive the call the scheduler than to do a 32-bit div.
The more divs we put it, the more expensive it all becomes.
What about:
if (delta_exec < sysctl_sched_min_granularity || delta_exec < __sched_gran(cfs_rq->nr_running))
This way we avoid the div when delta_exec is less than the min_granularity, and then we can do the div to perhaps avoid a needless resched?
-- Steve
Quoted 18 lines · * Steven Rostedt ([email protected]) wrote:
Quoted 6 lines · Peter Zijlstra
Quoted 5 lines
kernel/sched_fair.c dequeue_entity(struct cfs_rq *cfs_rq, st · line 870
Quoted 2 lines
kernel/sched_fair.c +0
-2-if (delta_exec < sysctl_sched_min_granularity) -return ;Well, the reason why this test is here seems to be that we don't want to trigger "
resched_task" more often than needed, and here it's defined by the granularity.Quoted 9 lines
Right, but its wrong for the weighted case. Letting a light task run that long will make its latency suck.
Quoted 3 lines
I don't quite see with what you are replacing this, other than "let's set the resched flag all the time to save a 32-bit division". I figure out it's more expensive the call the scheduler than to do a 32-bit div.
The more divs we put it, the more expensive it all becomes.
Quoted 8 lines
What about:
if (delta_exec < sysctl_sched_min_granularity || delta_exec < __sched_gran(cfs_rq->nr_running))This way we avoid the div when
delta_execis less than themin_granularity, and then we can do the div to perhaps avoid a needless resched?
Please note that my patch does not even take the 32-bit div when there are less than 4 threads running on the system.
So I'm not at all sure we're trying to optimize an important case here.
Mathieu
Quoted 4 lines
-- Steve
Signature · 4 lines
Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
Steven Rostedt
reviewerQuoted 8 lines · Mathieu Desnoyers
Quoted 8 lines
Quoted 2 lines
The more divs we put it, the more expensive it all becomes.
What about:
if (delta_exec < sysctl_sched_min_granularity || delta_exec < __sched_gran(cfs_rq->nr_running))
Quoted 8 lines
Quoted 3 lines
This way we avoid the div when
delta_execis less than themin_granularity, and then we can do the div to perhaps avoid a needless resched?Please note that my patch does not even take the 32-bit div when there are less than 4 threads running on the system.
So I'm not at all sure we're trying to optimize an important case here.
If we have 5 threads running and hit this where delta_exec is < sched_min_granularity, then we do have that div, right? Question is, how often do we hit this condition where delta_exec is less while running more that 4 threads?
-- Steve
RFC PATCH 1/1 check_preempt_tick should not compare vruntime with wall time
In reply to Peter ZijlstraQuoted 1 line · * Peter Zijlstra ([email protected]) wrote:
On Mon, 2010-09-13 at 09:56 -0400, Mathieu Desnoyers wrote:
[...]
Quoted 10 lines
Quoted 9 lines
Review
Quoted 5 lines
static void
check_preempt_tick(struct cfs_rq *cfs_rq, struct sched_entity *curr){(quoted diff) +1
-1- unsigned long ideal_runtime, delta_exec; + unsigned long slice = sched_slice(cfs_rq, curr);So you still compute the
sched_slice(), based onsched_period(), based onsysctl_sched_min_granularity*=nr_runningwhen there are more thannr_latencyrunning threads.
Quoted 8 lines
What's wrong with that? I keep asking you, you keep not giving an answer. Stop focussing on
nr_latency, its an by produce not a fundamental entity.period :=
max(latency, min_gran * nr_running)See, no
nr_latency-- the one and only purpose ofnr_latencyis avoiding that multiplication when possible.
OK, the long IRC discussions we just had convinced me that the current scheme takes things into account by adapting the granularity dynamically, but also got me to notice that check_preempt seems to compare vruntime with wall time, which is utterly incorrect. So maybe all my patch was doing was to expose this bug:
--- kernel/sched_fair.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/sched_fair.c +1 -1
@@ -869,7 +869,7 @@ check_preempt_tick(struct cfs_rq *cfs_rqstruct sched_entity *se =__pick_next_entity (cfs_rq);s64 delta = curr->vruntime - se->vruntime; -if (delta > ideal_runtime) +if (delta >calc_delta_fair (ideal_runtime, curr))resched_task (rq_of (cfs_rq)->curr); } }
Signature · 4 lines
Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
Re: [RFC PATCH] check_preempt_tick should not compare vruntime with wall time
Quoted 5 lines · Mathieu Desnoyers
OK, the long IRC discussions we just had convinced me that the current scheme takes things into account by adapting the granularity dynamically, but also got me to notice that
check_preemptseems to compare vruntime with wall time, which is utterly incorrect. So maybe all my patch was doing was to expose this bug:
Do you have latency numbers for this patch?
Linus
Re: [RFC PATCH] check_preempt_tick should not compare vruntime with wall time
Quoted 9 lines · * Linus Torvalds ([email protected]) wrote:
Quoted 5 lines · Mathieu Desnoyers
OK, the long IRC discussions we just had convinced me that the current scheme takes things into account by adapting the granularity dynamically, but also got me to notice that
check_preemptseems to compare vruntime with wall time, which is utterly incorrect. So maybe all my patch was doing was to expose this bug:Do you have latency numbers for this patch?
Sure, see below,
In addition to this patch, I also used Peter's approach of reducing the minimum granularity (given that now I am confident that the value of sysctl_sched_min_granularity won't affect the preemption granularity directly, but rather indirectly through the period length). The result, succinctly, is that just the "check_preempt" fix does not seem to do much difference in terms of fork wakeup latency (the results below give an order of magnitude, but should be taken with a grain of salt due to the noise). I ran 3 the tests 3 times each, and took the average, but there is clearly some noise.
FWIW, Xorg and firefox feel _much more_ responsive with the fix I propose when running with a make -j10. The system is even usable with a make -j20 on my UP machine, even though I can start feeling a some lag. This is probably a more important, yet less scientific, result.
It turns out that the min_granularity value (and hence the associated nr_latency values) have been brought from 20 down to 5
(commit 722aab0c3bbd7648d66790515c14d95d10a15bf3), and then down to 3 lately (commit 21406928afe43f1db6acab4931bb8c886f4d04ce). I would not be surprised that this last change might have been trying to hide the vruntime vs wall time comparison bug, which has been introduced in
commit f685ceacab07d3f6c236f04803e2f2f0dbcc5afb.
2.0GHz Pentium M
* wakeup-latency.c (SIGEV_THREAD) with make -j10
- Mainline 2.6.35.2 kernel
maximum latency: 45762.1 µs
average latency: 7348.6 µs
missed timer events: 0
- check_preempt fix
maximum latency: 39858.9 µs
average latency: 7728.1 µs
missed timer events: 0
- With only Peter's smaller min_gran (shown below):
maximum latency: 29100.6 µs
average latency: 6684.1 µs
missed timer events: 0
- check_preempt fix + Peter's smaller min_gran:
maximum latency: 20433.0 µs
average latency: 5112.5 µs
missed timer events: 0
Thanks,
Mathieu
Diminish min granularity patch:
--- kernel/sched_fair.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
kernel/sched_fair.c +3 -3
@@ -54,13 +54,13 @@ enum sched_tunable_scaling sysctl_sched_* Minimal preemption granularity for CPU-bound tasks: * (default: 2 msec * (1 + ilog(ncpus)), units: nanoseconds) */ -unsigned int sysctl_sched_min_granularity =2000000ULL ; -unsigned int normalized_sysctl_sched_min_granularity =2000000ULL ; +unsigned int sysctl_sched_min_granularity =750000ULL ; +unsigned int normalized_sysctl_sched_min_granularity =750000ULL ;/* * is kept at sysctl_sched_latency / sysctl_sched_min_granularity */ -static unsigned int sched_nr_latency =3 ; +static unsigned int sched_nr_latency =8 ;/* * After fork, child runs first. If set to 0 (default) then
Signature · 4 lines
Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
Re: [RFC PATCH] check_preempt_tick should not compare vruntime with wall time
Quoted 5 lines · Mathieu Desnoyers
FWIW, Xorg and firefox feel
_muchmore_responsive with the fix I propose when running with a make -j10. The system is even usable with a make -j20 on my UP machine, even though I can start feeling a some lag. This is probably a more important, yet less scientific, result.
I'll test that myself (but in a bit - I need to go do voter registration and socsec update first, though - I became a US citizen last week).
Because yes, that's the reason I'm personally interested in your scheduler latency work: I think our X behavior under load is pitiful (I do "make -j16" on my dual-core with HT Core i5, and web browsong shouldn't start to lag as much as it does just because I overcommit the CPU a bit). So if this makes a noticeable difference, I think it's very important.
Linus
Re: [RFC PATCH] check_preempt_tick should not compare vruntime with wall time
Quoted 11 lines · * Linus Torvalds ([email protected]) wrote:
Quoted 5 lines · Mathieu Desnoyers
FWIW, Xorg and firefox feel
_muchmore_responsive with the fix I propose when running with a make -j10. The system is even usable with a make -j20 on my UP machine, even though I can start feeling a some lag. This is probably a more important, yet less scientific, result.I'll test that myself (but in a bit - I need to go do voter registration and socsec update first, though - I became a US citizen last week).
Congratulations!
Quoted 6 lines
Because yes, that's the reason I'm personally interested in your scheduler latency work: I think our X behavior under load is pitiful (I do "make -j16" on my dual-core with HT Core i5, and web browsong shouldn't start to lag as much as it does just because I overcommit the CPU a bit). So if this makes a noticeable difference, I think it's very important.
Please make sure to include the "smaller min_granularity" patch in your test too, because the "check_preempt_tick" fix seems to only affect threads with non-zero nice value. I suspect that most of the responsiveness improvement I got is mainly from lowering the min_granularity.
Thanks,
Mathieu
Signature · 4 lines
Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
Steven Rostedt
reviewerRe: [RFC PATCH] check_preempt_tick should not compare vruntime with wall time
In reply to Linus TorvaldsQuoted 3 lines · Linus Torvalds
I'll test that myself (but in a bit - I need to go do voter registration and socsec update first, though - I became a US citizen last week).
Congrats!
-- Steve
Re: [RFC PATCH] check_preempt_tick should not compare vruntime with wall time
In reply to Mathieu DesnoyersQuoted 9 lines · Mathieu Desnoyers
Quoted 8 lines · * Linus Torvalds ([email protected]) wrote:
Quoted 5 lines · Mathieu Desnoyers
OK, the long IRC discussions we just had convinced me that the current scheme takes things into account by adapting the granularity dynamically, but also got me to notice that
check_preemptseems to compare vruntime with wall time, which is utterly incorrect. So maybe all my patch was doing was to expose this bug:
Quoted 5 lines
Quoted 1 line
Do you have latency numbers for this patch?
Sure, see below,
In addition to this patch, [...]
Note, which is a NOP for your latency workload.
Quoted 1 line
[...] I also used Peter's approach of reducing the minimum granularity
Ok, that's the very first patch i sent yesterday morning - so we also have my numbers that it reduces latencies.
To move things along i'll apply it with your Reported-by and Acked-by line, ok?
We can also work on the other, more complex things after that, but first lets make some progress on the latency front ...
Thanks,
Ingo
Re: [RFC PATCH] check_preempt_tick should not compare vruntime with wall time
Quoted 22 lines · * Ingo Molnar ([email protected]) wrote:
Quoted 9 lines · Mathieu Desnoyers
Quoted 8 lines · * Linus Torvalds ([email protected]) wrote:
Quoted 5 lines · Mathieu Desnoyers
OK, the long IRC discussions we just had convinced me that the current scheme takes things into account by adapting the granularity dynamically, but also got me to notice that
check_preemptseems to compare vruntime with wall time, which is utterly incorrect. So maybe all my patch was doing was to expose this bug:Quoted 5 lines
Quoted 1 line
Do you have latency numbers for this patch?
Sure, see below,
In addition to this patch, [...]
Note, which is a NOP for your latency workload.
Quoted 1 line
[...] I also used Peter's approach of reducing the minimum granularity
Quoted 8 lines
Ok, that's the very first patch i sent yesterday morning - so we also have my numbers that it reduces latencies.
To move things along i'll apply it with your Reported-by and Acked-by line, ok?
We can also work on the other, more complex things after that, but first lets make some progress on the latency front ...
Yep, that's fine with me.
Thanks!
Mathieu
Quoted 4 lines
Thanks,
Ingo
Signature · 4 lines
Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
PATCH 1/1 sched: Improve latencies under load by decreasing minimum scheduling granularity
Quoted 29 lines · Mathieu Desnoyers
Quoted 28 lines · * Ingo Molnar ([email protected]) wrote:
Quoted 9 lines · Mathieu Desnoyers
Quoted 8 lines · * Linus Torvalds ([email protected]) wrote:
Quoted 5 lines · Mathieu Desnoyers
OK, the long IRC discussions we just had convinced me that the current scheme takes things into account by adapting the granularity dynamically, but also got me to notice that
check_preemptseems to compare vruntime with wall time, which is utterly incorrect. So maybe all my patch was doing was to expose this bug:Quoted 5 lines
Quoted 1 line
Do you have latency numbers for this patch?
Sure, see below,
In addition to this patch, [...]
Note, which is a NOP for your latency workload.
Quoted 1 line
[...] I also used Peter's approach of reducing the minimum granularity
Ok, that's the very first patch i sent yesterday morning - so we also have my numbers that it reduces latencies.
To move things along i'll apply it with your Reported-by and Acked-by line, ok?
Quoted 6 lines
Quoted 2 lines
We can also work on the other, more complex things after that, but first lets make some progress on the latency front ...
Yep, that's fine with me.
Thanks!
You are welcome!
Linus, Mathieu, you can test the granularity reduction patch via:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git sched/urgent
Patch also attached below.
Note, i'd like to keep this separate from the check_preempt() change - which only affects reniced tasks and isnt essential to these tests. (we want such things to be in separate commits, for bisectability)
Thanks,
Ingo
------------------>
Ingo Molnar (1):
sched: Improve latencies under load by decreasing minimum scheduling granularity
kernel/sched_fair.c | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-)
kernel/sched_fair.c +3 -3
@@ -54,13 +54,13 @@ enum sched_tunable_scaling sysctl_sched_tunable_scaling* Minimal preemption granularity for CPU-bound tasks: * (default: 2 msec * (1 + ilog(ncpus)), units: nanoseconds) */ -unsigned int sysctl_sched_min_granularity =2000000ULL ; -unsigned int normalized_sysctl_sched_min_granularity =2000000ULL ; +unsigned int sysctl_sched_min_granularity =750000ULL ; +unsigned int normalized_sysctl_sched_min_granularity =750000ULL ;/* * is kept at sysctl_sched_latency / sysctl_sched_min_granularity */ -static unsigned int sched_nr_latency =3 ; +static unsigned int sched_nr_latency =8 ;/* * After fork, child runs first. If set to 0 (default) then
Re: [PATCH] sched: Improve latencies under load by decreasing minimum scheduling granularity
kernel/sched_fair.c enum sched_tunable_scaling sysctl_sched_tunable_scaling · line 58
Quoted 10 lines · Ingo Molnar
sched: Improve latencies under load by decreasing minimum scheduling granularity
kernel/sched_fair.c | 6 +++---kernel/sched_fair.c +2
-2@@ -54,13 +54,13 @@ enum sched_tunable_scaling sysctl_sched_tunable_scaling* Minimal preemption granularity for CPU-bound tasks: * (default: 2 msec * (1 + ilog(ncpus)), units: nanoseconds) */ -unsigned int sysctl_sched_min_granularity =2000000ULL ; -unsigned int normalized_sysctl_sched_min_granularity =2000000ULL ; +unsigned int sysctl_sched_min_granularity =750000ULL ; +unsigned int normalized_sysctl_sched_min_granularity =750000ULL ;
Change the comment as well?
Re: [PATCH] sched: Improve latencies under load by decreasing minimum scheduling granularity
In reply to Ingo MolnarQuoted 2 lines · Ingo Molnar
Linus, Mathieu, you can test the granularity reduction patch via:
Hmm. It's a bit hard to judge subjective feelings, especially when you have expectations of improvement, but yes, I think this does improve the the interactive feel when scroll-wheeling around in firefox or chrome.
So on the whole I'd trust the actual latency benchmark numbers more, but I _think_ it does translate into actually feeling better too.
Linus
Re: [PATCH] sched: Improve latencies under load by decreasing minimum scheduling granularity
Quoted 8 lines · Linus Torvalds
Quoted 2 lines · Ingo Molnar
Linus, Mathieu, you can test the granularity reduction patch via:
Hmm. It's a bit hard to judge subjective feelings, especially when you have expectations of improvement, but yes, I think this does improve the the interactive feel when scroll-wheeling around in firefox or chrome.
Yeah. Human perception generally notices the _gradient_ of behavior - i.e. the difference between the best-case and worst-case behavior. I.e. we notice the max latencies - and those came down distinctly in everyone's measurements.
Somewhat paradoxially, 'always slow' is generally felt as an improvement over 'sometimes fast, sometimes slow' - even though the latter has a better average. (as long as 'slow' is not 'intolerably slow')
Quoted 2 lines
So on the whole I'd trust the actual latency benchmark numbers more, but I _think_ it does translate into actually feeling better too.
Ok, great - would you like to have this in v2.6.36 (in which case feel free to pull it now), or v2.6.37?
I'm hopeful that the other patches in the works will give more improvements - i dont actually like the relatively high noise that the max latencies produce - i think we should be more deterministic/dependable there. But those changes are also more complex, so they will take a bit more time to finish - and it's definitely v2.6.37 fodder.
Thanks,
Ingo
Re: [RFC PATCH] check_preempt_tick should not compare vruntime with wall time
In reply to Mathieu DesnoyersQuoted 10 lines · Mathieu Desnoyers
2.0GHz Pentium M
*
wakeup-latency.c(SIGEV_THREAD) with make -j10- Mainline 2.6.35.2 kernel
maximum latency: 45762.1 µs
average latency: 7348.6 µs
missed timer events: 0
Quoted 5 lines
-
check_preemptfixmaximum latency: 39858.9 µs
average latency: 7728.1 µs
missed timer events: 0
Note that the check_preempt fix, as i mentioned it in the previous mail, has no effect on this workload - so any effect you see is pure noise.
Quoted 5 lines
- With only Peter's smaller
min_gran(shown below):maximum latency: 29100.6 µs
average latency: 6684.1 µs
missed timer events: 0
That's the real improvement.
Quoted 4 lines
-
check_preemptfix + Peter's smallermin_gran:
maximum latency: 20433.0 µs
average latency: 5112.5 µs
missed timer events: 0
Again, pure noise effect.
Ingo
Re: [RFC PATCH] check_preempt_tick should not compare vruntime with wall time
In reply to Mathieu DesnoyersQuoted 37 lines · Mathieu Desnoyers
Quoted 1 line · * Peter Zijlstra ([email protected]) wrote:
On Mon, 2010-09-13 at 09:56 -0400, Mathieu Desnoyers wrote:
[...]
Quoted 10 lines
Quoted 9 lines
Review
Quoted 5 lines
static void
check_preempt_tick(struct cfs_rq *cfs_rq, struct sched_entity *curr){(quoted diff) +1
-1- unsigned long ideal_runtime, delta_exec; + unsigned long slice = sched_slice(cfs_rq, curr);So you still compute the
sched_slice(), based onsched_period(), based onsysctl_sched_min_granularity*=nr_runningwhen there are more thannr_latencyrunning threads.Quoted 8 lines
What's wrong with that? I keep asking you, you keep not giving an answer. Stop focussing on
nr_latency, its an by produce not a fundamental entity.period :=
max(latency, min_gran * nr_running)See, no
nr_latency-- the one and only purpose ofnr_latencyis avoiding that multiplication when possible.OK, the long IRC discussions we just had convinced me that the current scheme takes things into account by adapting the granularity dynamically, but also got me to notice that
check_preemptseems to compare vruntime with wall time, which is utterly incorrect. So maybe all my patch was doing was to expose this bug:--- kernel/sched_fair.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)Index:
linux-2.6-lttng.git/kernel/sched_fair.c
===================================================================
kernel/sched_fair.c check_preempt_tick(struct cfs_rq *cfs_rq · line 875
Quoted 8 lines
kernel/sched_fair.c +1
-1@@ -869,7 +869,7 @@ check_preempt_tick(struct cfs_rq *cfs_rqstruct sched_entity *se =__pick_next_entity (cfs_rq);s64 delta = curr->vruntime - se->vruntime; -if (delta > ideal_runtime) +if (delta >calc_delta_fair (ideal_runtime, curr))resched_task (rq_of (cfs_rq)->curr); } }
It should have no effect at all on your latency measurements, as calc_delta_fair() is a NOP for nice-0 tasks:
static inline unsigned long calc_delta_fair(unsigned long delta, struct sched_entity *se)
{
if (unlikely(se->load.weight != NICE_0_LOAD))
delta = calc_delta_mine(delta, NICE_0_LOAD, &se->load);
return delta;}
Thanks,
Ingo
Re: [RFC PATCH] check_preempt_tick should not compare vruntime with wall time
Quoted 52 lines · * Ingo Molnar ([email protected]) wrote:
Quoted 37 lines · Mathieu Desnoyers
Quoted 1 line · * Peter Zijlstra ([email protected]) wrote:
On Mon, 2010-09-13 at 09:56 -0400, Mathieu Desnoyers wrote:
[...]
Quoted 10 lines
Quoted 9 lines
Review
Quoted 5 lines
static void
check_preempt_tick(struct cfs_rq *cfs_rq, struct sched_entity *curr){(quoted diff) +1
-1- unsigned long ideal_runtime, delta_exec; + unsigned long slice = sched_slice(cfs_rq, curr);So you still compute the
sched_slice(), based onsched_period(), based onsysctl_sched_min_granularity*=nr_runningwhen there are more thannr_latencyrunning threads.Quoted 8 lines
What's wrong with that? I keep asking you, you keep not giving an answer. Stop focussing on
nr_latency, its an by produce not a fundamental entity.period :=
max(latency, min_gran * nr_running)See, no
nr_latency-- the one and only purpose ofnr_latencyis avoiding that multiplication when possible.OK, the long IRC discussions we just had convinced me that the current scheme takes things into account by adapting the granularity dynamically, but also got me to notice that
check_preemptseems to compare vruntime with wall time, which is utterly incorrect. So maybe all my patch was doing was to expose this bug:--- kernel/sched_fair.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)Index:
linux-2.6-lttng.git/kernel/sched_fair.c
===================================================================kernel/sched_fair.c check_preempt_tick(struct cfs_rq *cfs_rq · line 875
Quoted 8 lines
kernel/sched_fair.c +1
-1@@ -869,7 +869,7 @@ check_preempt_tick(struct cfs_rq *cfs_rqstruct sched_entity *se =__pick_next_entity (cfs_rq);s64 delta = curr->vruntime - se->vruntime; -if (delta > ideal_runtime) +if (delta >calc_delta_fair (ideal_runtime, curr))resched_task (rq_of (cfs_rq)->curr); } }It should have no effect at all on your latency measurements, as
calc_delta_fair()is a NOP for nice-0 tasks:
Quoted 8 lines
static inline unsigned long
calc_delta_fair(unsigned long delta, struct sched_entity *se){ if (unlikely(se->load.weight != NICE_0_LOAD)) delta = calc_delta_mine(delta, NICE_0_LOAD, &se->load); return delta;}
That's right. My latency measurements stay roughly the same (see my email to Linus). As for Xorg responsiveness, this is not based on some scientifically proven data (only my impression). My Xorg is running as nice 0 too.
So the effect of this vruntime vs wall time comparison would just be that tasks with non-zero positive nice level would run for longer slices, and tasks with negative nice level would run for shorter slices, am I correct ?
Thanks,
Mathieu
Quoted 4 lines
Thanks,
Ingo
Signature · 4 lines
Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
Re: [RFC PATCH] check_preempt_tick should not compare vruntime with wall time
In reply to Mathieu DesnoyersQuoted 19 lines · Mathieu Desnoyers
Quoted 1 line · * Peter Zijlstra ([email protected]) wrote:
On Mon, 2010-09-13 at 09:56 -0400, Mathieu Desnoyers wrote:
[...]
Quoted 16 lines
Quoted 9 lines
Review
Quoted 5 lines
static void
check_preempt_tick(struct cfs_rq *cfs_rq, struct sched_entity *curr){(quoted diff) +1
-1- unsigned long ideal_runtime, delta_exec; + unsigned long slice = sched_slice(cfs_rq, curr);So you still compute the
sched_slice(), based onsched_period(), based onsysctl_sched_min_granularity*=nr_runningwhen there are more thannr_latencyrunning threads.What's wrong with that? I keep asking you, you keep not giving an answer. Stop focussing on
nr_latency, its an by produce not a fundamental entity.period :=
max(latency, min_gran * nr_running)
Quoted 7 lines
Quoted 2 lines
See, no
nr_latency-- the one and only purpose ofnr_latencyis avoiding that multiplication when possible.OK, the long IRC discussions we just had convinced me that the current scheme takes things into account by adapting the granularity dynamically, but also got me to notice that
check_preemptseems to compare vruntime with wall time, which is utterly incorrect. So maybe all my patch was doing was to expose this bug:
It's not wall time, it's just a distance. But I'm not attached to it by any means, if something else works better, do that :)
-Mike
Quoted 9 lines · Mathieu Desnoyers
Quoted 7 lines · * Peter Zijlstra ([email protected]) wrote:
One option is to simply get rid of that stuff in
check_preempt_tick()and instead do a wakeup-preempt check on the leftmost task instead.The code as it stands today does that
delta_exec<min_grancheck to ensure current gets some runtime before doing that second preemption check, which compares vruntime with a wall-time measure.
Quoted 7 lines
Quoted 3 lines
Making that gran more complex doesn't really buy us much because for a system with different weights in the gran and slice lengths don't match up anyway.
So I bet this last sentence is about the example of a system with many nice 19 processes I told you about on IRC. Yes, this one is a bummer, as we would not like to count them as running threads at all.
Tick doesn't help much with nice 19, tick is much larger than slice, so barring wakeup preemption, nice 19 tasks should _slam_ right when the tick finally arrives.
Quoted 7 lines
Quoted 7 lines
kernel/sched_fair.c +2
-3/* -* Ensure that a task that missed wakeup preemption by a -* narrow margin doesn't have to wait for a full slice. -* This also mitigates buddy induced latencies under load. +* The current task ran long enough, ensure it doesn't get +* re-elected due to buddy favours. */
Quoted 8 lines
kernel/sched_fair.c dequeue_entity(struct cfs_rq *cfs_rq, st · line 870
Quoted 5 lines
kernel/sched_fair.c +0
-5-if (!sched_feat (WAKEUP_PREEMPT )) -return ; - -if (delta_exec < sysctl_sched_min_granularity) -return ;Well, the reason why this test is here seems to be that we don't want to trigger "
resched_task" more often than needed...
Yeah. Heavily niced tasks would usually be booted before we got this far because of small slices, just making sure to not evict some first class citizen _too_ soon while trying to reduce latency a bit. If a heavily niced task slips through, oh darn, but it did before too.
-Mike
A message that is not in the archive (sent off-list or not yet received): [email protected]
Peter Zijlstra
maintainerQuoted 6 lines · Mike Galbraith
Quoted 2 lines
One option is to simply get rid of that stuff in
check_preempt_tick()and instead do a wakeup-preempt check on the leftmost task instead.That's what I wanted to boil it down to instead of putting the extra preempt check in, but it kills the longish slices of low load. IIRC, when I tried that, it demolished throughput.
Hrm.. yes it would..
So the reason for all this:
/*
* Ensure that a task that missed wakeup preemption by a
* narrow margin doesn't have to wait for a full slice.
* This also mitigates buddy induced latencies under load. */
Is to avoid tasks getting too far ahead in virtual time due to buddies, right?
Would something like the below work? Don't actually use delta_exec to filter, but use wakeup_gran + min_gran on virtual time, (much like Steve suggested) and then verify using __sched_gran().
Or have I now totally confused myself backwards?
- delta_exec is walltime, and should thus we compared against a weighted unit like slice,
- delta is a vruntime unit, and is thus weight free, hence we can use granularity/unweighted units.
--- kernel/sched_fair.c | 20 ++++++++++++++++---- 1 files changed, 16 insertions(+), 4 deletions(-)
kernel/sched_fair.c +16 -4
@@ -485,6 +485,16 @@ static u64 sched_slice(struct cfs_rq *cfs_rq, struct sched_entity *se)return slice; } +static u64 __sched_gran (unsigned long nr_running) +{ +unsigned long latency = sysctl_sched_latency; + +if (nr_running >= nr_latency) +return sysctl_sched_min_granularity; + +return latency / nr_running; +} +/* * We calculate the vruntime slice of a to be inserted task *
@@ -865,14 +875,16 @@ check_preempt_tick(struct cfs_rq *cfs_rq, struct sched_entity *curr)if (!sched_feat (WAKEUP_PREEMPT ))return ; -if (delta_exec < sysctl_sched_min_granularity) -return ; -if (cfs_rq->nr_running >1 ) {struct sched_entity *se =__pick_next_entity (cfs_rq);s64 delta = curr->vruntime - se->vruntime; +u64 wakeup_gran = sysctl_sched_wakeup_granularity; +u64 min_gran = sysctl_sched_min_granularity; + +if (delta < wakeup_gran + min_gran) +return ; -if (delta > ideal_runtime) +if (delta > wakeup_gran +__sched_gran (cfs_rq->nr_running))resched_task (rq_of (cfs_rq)->curr); } }
Peter Zijlstra
maintainerRFC PATCH 1/1 sched: Improve tick preemption
On an SMP machine, but sysctl knobs adjusted as if it were UP and everything ran with schedtool -a1
For workload I used: make O=defconfig-build -j10 kernel/
(full bzImage builds take like forever with a single cpu, runs were done cache-hot)
Normal:
# for i in {latency,min_granularity,wakeup_granularity}; do cat sched_${i}_ns; done
6000000
2000000
1000000#schedtool -a1 -e ./wakeup-latency
maximum latency: 22169.0 µs
average latency: 1559.8 µs
missed timer events: 0
# for i in {latency,min_granularity,wakeup_granularity}; do cat sched_${i}_ns; done
6000000
750000
1000000# schedtool -a1 -e ./wakeup-latency maximum latency: 11999.9 µs average latency: 710.9 µs missed timer events: 0
Patched:
# for i in {latency,min_granularity,wakeup_granularity}; do cat sched_${i}_ns; done
6000000
2000000
1000000maximum latency: 18042.3 µs
average latency: 2729.3 µs
missed timer events: 0
# for i in {latency,min_granularity,wakeup_granularity}; do cat sched_${i}_ns; done
6000000
750000
1000000maximum latency: 9985.8 µs
average latency: 551.4 µs
missed timer events: 0
Could others try and reproduce this while I try and run a few other benchmarks?
---
Subject: sched: Improve tick preemption
Regular tick preemption has a few issues:
- it compares delta_exec (wall-time) with an unweighted measure (min_gran)
- that min_gran might be too small for systems with a small number of tasks.
Cure the first issue by instead comparing the vruntime (virtual time) difference with this unweighted measure.
Cure the second issue by computing the actual granularity for small systems.
--- kernel/sched_fair.c | 17 +++++++++++++---- 1 files changed, 13 insertions(+), 4 deletions(-)
kernel/sched_fair.c +13 -4
@@ -457,6 +457,16 @@ static u64 __sched_period(unsigned long nr_running)return period; } +static u64 __sched_gran (unsigned long nr_running) +{ +unsigned long latency = sysctl_sched_latency; + +if (nr_running >= sched_nr_latency) +return sysctl_sched_min_granularity; + +return latency / nr_running; +} +/* * We calculate the wall-time slice from the period by taking a part * proportional to the weight.
@@ -865,14 +875,13 @@ check_preempt_tick(struct cfs_rq *cfs_rq, struct sched_entity *curr)if (!sched_feat (WAKEUP_PREEMPT ))return ; -if (delta_exec < sysctl_sched_min_granularity) -return ; -if (cfs_rq->nr_running >1 ) {struct sched_entity *se =__pick_next_entity (cfs_rq);s64 delta = curr->vruntime - se->vruntime; +if (delta < sysctl_sched_min_granularity) +return ; -if (delta > ideal_runtime) +if (delta >__sched_gran (cfs_rq->nr_running))resched_task (rq_of (cfs_rq)->curr); } }
Quoted 12 lines · Peter Zijlstra
Quoted 6 lines · Mike Galbraith
Quoted 2 lines
One option is to simply get rid of that stuff in
check_preempt_tick()and instead do a wakeup-preempt check on the leftmost task instead.That's what I wanted to boil it down to instead of putting the extra preempt check in, but it kills the longish slices of low load. IIRC, when I tried that, it demolished throughput.
Hrm.. yes it would..
So the reason for all this:
Quoted 8 lines
/*
* Ensure that a task that missed wakeup preemption by a
* narrow margin doesn't have to wait for a full slice.
* This also mitigates buddy induced latencies under load. */Is to avoid tasks getting too far ahead in virtual time due to buddies, right?
Yeah, that was the thought anyway.
Quoted 10 lines
Would something like the below work? Don't actually use
delta_execto filter, but usewakeup_gran+min_granon virtual time, (much like Steve suggested) and then verify using__sched_gran().Or have I now totally confused myself backwards?
-
delta_execis walltime, and should thus we compared against a weighted unit like slice,
- delta is a vruntime unit, and is thus weight free, hence we can use granularity/unweighted units.
I don't think it really matters. Distance is weighted when using slice as the measure.
-Mike
Quoted 10 lines · Mathieu Desnoyers
(on a uniprocessor 2.0 GHz Pentium M)
* Without the patch:
- wakeup-latency with
SIGEV_THREADin parallel with youtube video and make -j10maximum latency: 50107.8 µs
average latency: 6609.2 µs
missed timer events: 0
I tried your patches on a similar UP system, using wakeup-latency.c. I also measured the vanilla upstream kernel (cced86a) with the default granularity settings, and also vanilla with a sched_min_granularity/3 tune (patch attached below for that).
I got the following results (make -j10 kbuild load, average of 3 runs):
vanilla:
maximum latency: 38278.9 µs
average latency: 7730.1 µs
mathieu-dyn:
maximum latency: 28698.8 µs
average latency: 7757.1 µs
peterz-min_gran/3:
maximum latency: 22702.1 µs
average latency: 6684.8 µs
A couple of notes:
- As can be seen from the raw results further below, the max-latency sched-latency.c numbers were very noisy with all 3 kernels. (This is typical of most maxium latency metrics). But it can be said that within statistical noise both your patches and peterz's patch reduced maximum latencies - as expected.
- average latency seems to have gone down a bit more via the min_gran/3 patch. Your patch produced a faster-than-vanilla result in one of the runs - but the numbers are too noisy in general.
- ( Measurement methodology: find below the raw results of the 3 runs pasted, and find attached the kernel config i used. (I applied your second patch with a trivial conflict resolved.) For measurement i used:
your scheduling latency benchmark:
http://www.efficios.com/pub/elc2010/wakeup-latency-0.1.tar.bz2 )
In general, your patches have indeed produced a max-latency improvement
- and so has the simpler min_gran/3 patch too.
So as Peter has suggested in his review, much of the same latency improvement can be gotten by the implicit /3 tune your patches do to min-granularity.
So perhaps it would be better to investigate/measure your series by making the min_gran/3 patch below your patch #1 - and thus your other changes (the nr_running dependency) could be evaluated relative to that.
I.e. please re-phrase your series as: "what else does it give us beyond tuning down the minimum granularity to 33% of its current value?"
Your patches might have further merit than these numbers alone show - here i tried to limit my measurements to the measurements you yourself used. Maybe your approach can handle the granularity tradeoffs better in some other workload, etc.
Thanks,
Ingo
---------------------------->
vanilla (cced86a):
maximum latency: 46980.9 µs
average latency: 7696.9 µs
missed timer events: 0
maximum latency: 35636.3 µs
average latency: 7736.6 µs
missed timer events: 0
maximum latency: 32219.6 µs
average latency: 7757.0 µs
mathieu-dyn (cced86a+the-2-patches-in-this-thread):
maximum latency: 33999.4 µs
average latency: 9410.9 µs
missed timer events: 0
maximum latency: 26125.7 µs
average latency: 7083.2 µs
missed timer events: 0
maximum latency: 25971.5 µs
average latency: 6777.3 µs
missed timer events: 0
peterz-min_gran/3 (cced86a+the-patch-attached-below):
maximum latency: 22366.3 µs
average latency: 7163.5 µs
missed timer events: 0
maximum latency: 15166.4 µs
average latency: 6788.6 µs
missed timer events: 0
maximum latency: 30573.8 µs
average latency: 6102.5 µs
--- kernel/sched_fair.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
kernel/sched_fair.c +3 -3
@@ -54,13 +54,13 @@ enum sched_tunable_scaling sysctl_sched_* Minimal preemption granularity for CPU-bound tasks: * (default: 2 msec * (1 + ilog(ncpus)), units: nanoseconds) */ -unsigned int sysctl_sched_min_granularity =2000000ULL ; -unsigned int normalized_sysctl_sched_min_granularity =2000000ULL ; +unsigned int sysctl_sched_min_granularity =750000ULL ; +unsigned int normalized_sysctl_sched_min_granularity =750000ULL ;/* * is kept at sysctl_sched_latency / sysctl_sched_min_granularity */ -static unsigned int sched_nr_latency =3 ; +static unsigned int sched_nr_latency =8 ;/* * After fork, child runs first. If set to 0 (default) then
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.36-rc3
# Mon Sep 13 00:28:11 2010
#CONFIG_64BIT=y
# CONFIG_X86_32 is not setCONFIG_X86_64=yCONFIG_X86=yCONFIG_INSTRUCTION_DECODER=yCONFIG_OUTPUT_FORMAT="elf64-x86-64"CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"CONFIG_GENERIC_CMOS_UPDATE=yCONFIG_CLOCKSOURCE_WATCHDOG=yCONFIG_GENERIC_CLOCKEVENTS=yCONFIG_GENERIC_CLOCKEVENTS_BROADCAST=yCONFIG_LOCKDEP_SUPPORT=yCONFIG_STACKTRACE_SUPPORT=yCONFIG_HAVE_LATENCYTOP_SUPPORT=yCONFIG_MMU=yCONFIG_ZONE_DMA=yCONFIG_NEED_DMA_MAP_STATE=yCONFIG_NEED_SG_DMA_LENGTH=yCONFIG_GENERIC_ISA_DMA=yCONFIG_GENERIC_IOMAP=yCONFIG_GENERIC_BUG=yCONFIG_GENERIC_BUG_RELATIVE_POINTERS=yCONFIG_GENERIC_HWEIGHT=yCONFIG_ARCH_MAY_HAVE_PC_FDC=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not setCONFIG_RWSEM_XCHGADD_ALGORITHM=yCONFIG_ARCH_HAS_CPU_IDLE_WAIT=yCONFIG_GENERIC_CALIBRATE_DELAY=yCONFIG_GENERIC_TIME_VSYSCALL=yCONFIG_ARCH_HAS_CPU_RELAX=yCONFIG_ARCH_HAS_DEFAULT_IDLE=yCONFIG_ARCH_HAS_CACHE_LINE_SIZE=yCONFIG_HAVE_SETUP_PER_CPU_AREA=yCONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=yCONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
# CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not setCONFIG_ARCH_HIBERNATION_POSSIBLE=yCONFIG_ARCH_SUSPEND_POSSIBLE=yCONFIG_ZONE_DMA32=yCONFIG_ARCH_POPULATES_NODE_MAP=yCONFIG_AUDIT_ARCH=yCONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=yCONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=yCONFIG_HAVE_EARLY_RES=yCONFIG_GENERIC_HARDIRQS=yCONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=yCONFIG_GENERIC_IRQ_PROBE=yCONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11" # CONFIG_KTIME_SCALAR is not setCONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"CONFIG_CONSTRUCTORS=y
#
# General setup
#CONFIG_EXPERIMENTAL=yCONFIG_BROKEN_ON_SMP=yCONFIG_INIT_ENV_ARG_LIMIT=32CONFIG_CROSS_COMPILE=""CONFIG_LOCALVERSION=""CONFIG_LOCALVERSION_AUTO=yCONFIG_HAVE_KERNEL_GZIP=yCONFIG_HAVE_KERNEL_BZIP2=yCONFIG_HAVE_KERNEL_LZMA=yCONFIG_HAVE_KERNEL_LZO=yCONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_LZO is not setCONFIG_SWAP=yCONFIG_SYSVIPC=yCONFIG_SYSVIPC_SYSCTL=yCONFIG_POSIX_MQUEUE=yCONFIG_POSIX_MQUEUE_SYSCTL=yCONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
# CONFIG_TASKSTATS is not set
# CONFIG_AUDIT is not set
#
# RCU Subsystem
#CONFIG_TREE_RCU=y
# CONFIG_TINY_RCU is not set
# CONFIG_RCU_TRACE is not setCONFIG_RCU_FANOUT=64
# CONFIG_RCU_FANOUT_EXACT is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_IKCONFIG is not setCONFIG_LOG_BUF_SHIFT=18CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
# CONFIG_CGROUPS is not setCONFIG_SYSFS_DEPRECATED=yCONFIG_SYSFS_DEPRECATED_V2=yCONFIG_RELAY=yCONFIG_NAMESPACES=y
# CONFIG_UTS_NS is not set
# CONFIG_IPC_NS is not set
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
# CONFIG_NET_NS is not setCONFIG_BLK_DEV_INITRD=yCONFIG_INITRAMFS_SOURCE=""CONFIG_RD_GZIP=yCONFIG_RD_BZIP2=yCONFIG_RD_LZMA=yCONFIG_RD_LZO=yCONFIG_CC_OPTIMIZE_FOR_SIZE=yCONFIG_SYSCTL=yCONFIG_ANON_INODES=y
# CONFIG_EMBEDDED is not setCONFIG_UID16=yCONFIG_SYSCTL_SYSCALL=yCONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not setCONFIG_KALLSYMS_EXTRA_PASS=yCONFIG_HOTPLUG=yCONFIG_PRINTK=yCONFIG_BUG=yCONFIG_ELF_CORE=yCONFIG_PCSPKR_PLATFORM=yCONFIG_BASE_FULL=yCONFIG_FUTEX=yCONFIG_EPOLL=yCONFIG_SIGNALFD=yCONFIG_TIMERFD=yCONFIG_EVENTFD=yCONFIG_SHMEM=yCONFIG_AIO=yCONFIG_HAVE_PERF_EVENTS=y
#
# Kernel Performance Events And Counters
#CONFIG_PERF_EVENTS=yCONFIG_PERF_COUNTERS=y
# CONFIG_DEBUG_PERF_USE_VMALLOC is not setCONFIG_VM_EVENT_COUNTERS=yCONFIG_PCI_QUIRKS=yCONFIG_SLUB_DEBUG=y
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not setCONFIG_SLUB=yCONFIG_PROFILING=yCONFIG_TRACEPOINTS=yCONFIG_OPROFILE=y
# CONFIG_OPROFILE_EVENT_MULTIPLEX is not setCONFIG_HAVE_OPROFILE=yCONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=yCONFIG_HAVE_IOREMAP_PROT=yCONFIG_HAVE_KPROBES=yCONFIG_HAVE_KRETPROBES=yCONFIG_HAVE_OPTPROBES=yCONFIG_HAVE_ARCH_TRACEHOOK=yCONFIG_HAVE_DMA_ATTRS=yCONFIG_HAVE_REGS_AND_STACK_ACCESS_API=yCONFIG_HAVE_DMA_API_DEBUG=yCONFIG_HAVE_HW_BREAKPOINT=yCONFIG_HAVE_MIXED_BREAKPOINTS_REGS=yCONFIG_HAVE_USER_RETURN_NOTIFIER=yCONFIG_HAVE_PERF_EVENTS_NMI=y
#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not setCONFIG_SLABINFO=yCONFIG_RT_MUTEXES=yCONFIG_BASE_SMALL=0
# CONFIG_MODULES is not setCONFIG_BLOCK=yCONFIG_BLK_DEV_BSG=y
# CONFIG_BLK_DEV_INTEGRITY is not setCONFIG_BLOCK_COMPAT=y
#
# IO Schedulers
#CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq"
# CONFIG_INLINE_SPIN_TRYLOCK is not set
# CONFIG_INLINE_SPIN_TRYLOCK_BH is not set # CONFIG_INLINE_SPIN_LOCK is not set
# CONFIG_INLINE_SPIN_LOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK_IRQ is not set
# CONFIG_INLINE_SPIN_LOCK_IRQSAVE is not set CONFIG_INLINE_SPIN_UNLOCK=y
# CONFIG_INLINE_SPIN_UNLOCK_BH is not set CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
# CONFIG_INLINE_SPIN_UNLOCK_IRQRESTORE is not set # CONFIG_INLINE_READ_TRYLOCK is not set
# CONFIG_INLINE_READ_LOCK is not set
# CONFIG_INLINE_READ_LOCK_BH is not set
# CONFIG_INLINE_READ_LOCK_IRQ is not set
# CONFIG_INLINE_READ_LOCK_IRQSAVE is not set CONFIG_INLINE_READ_UNLOCK=y
# CONFIG_INLINE_READ_UNLOCK_BH is not set CONFIG_INLINE_READ_UNLOCK_IRQ=y
# CONFIG_INLINE_READ_UNLOCK_IRQRESTORE is not set # CONFIG_INLINE_WRITE_TRYLOCK is not set
# CONFIG_INLINE_WRITE_LOCK is not set
# CONFIG_INLINE_WRITE_LOCK_BH is not set
# CONFIG_INLINE_WRITE_LOCK_IRQ is not set # CONFIG_INLINE_WRITE_LOCK_IRQSAVE is not set CONFIG_INLINE_WRITE_UNLOCK=y
# CONFIG_INLINE_WRITE_UNLOCK_BH is not set CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
# CONFIG_INLINE_WRITE_UNLOCK_IRQRESTORE is not set # CONFIG_MUTEX_SPIN_ON_OWNER is not set
# CONFIG_FREEZER is not set
#
# Processor type and features
#CONFIG_TICK_ONESHOT=yCONFIG_NO_HZ=yCONFIG_HIGH_RES_TIMERS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
# CONFIG_SMP is not set
# CONFIG_SPARSE_IRQ is not set CONFIG_X86_MPPARSE=y
# CONFIG_X86_EXTENDED_PLATFORM is not set CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y CONFIG_SCHED_OMIT_FRAME_POINTER=y
# CONFIG_PARAVIRT_GUEST is not set CONFIG_NO_BOOTMEM=y
# CONFIG_MEMTEST is not set
# CONFIG_MK8 is not set
# CONFIG_MPSC is not setCONFIG_MCORE2=y
# CONFIG_MATOM is not set
# CONFIG_GENERIC_CPU is not set CONFIG_X86_CPU=y CONFIG_X86_INTERNODE_CACHE_SHIFT=6 CONFIG_X86_CMPXCHG=y CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_XADD=yCONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_P6_NOP=yCONFIG_X86_TSC=yCONFIG_X86_CMPXCHG64=yCONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=64 CONFIG_X86_DEBUGCTLMSR=y CONFIG_CPU_SUP_INTEL=yCONFIG_CPU_SUP_AMD=y CONFIG_CPU_SUP_CENTAUR=yCONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=yCONFIG_DMI=yCONFIG_GART_IOMMU=yCONFIG_CALGARY_IOMMU=y
# CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT is not set # CONFIG_AMD_IOMMU is not set CONFIG_SWIOTLB=yCONFIG_IOMMU_HELPER=y
# CONFIG_IOMMU_API is not set CONFIG_NR_CPUS=1CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set CONFIG_X86_LOCAL_APIC=yCONFIG_X86_IO_APIC=y
# CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS is not set CONFIG_X86_MCE=yCONFIG_X86_MCE_INTEL=y
# CONFIG_X86_MCE_AMD is not set CONFIG_X86_MCE_THRESHOLD=y
# CONFIG_X86_MCE_INJECT is not set CONFIG_X86_THERMAL_VECTOR=y
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set CONFIG_X86_MSR=yCONFIG_X86_CPUID=y CONFIG_ARCH_PHYS_ADDR_T_64BIT=y CONFIG_DIRECT_GBPAGES=y CONFIG_ARCH_PROC_KCORE_TEXT=y CONFIG_ARCH_SPARSEMEM_DEFAULT=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000 CONFIG_SELECT_MEMORY_MODEL=y CONFIG_SPARSEMEM_MANUAL=yCONFIG_SPARSEMEM=y CONFIG_HAVE_MEMORY_PRESENT=y CONFIG_SPARSEMEM_EXTREME=y CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER=y CONFIG_SPARSEMEM_VMEMMAP=y
# CONFIG_MEMORY_HOTPLUG is not set CONFIG_PAGEFLAGS_EXTENDED=y CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_COMPACTION is not set CONFIG_PHYS_ADDR_T_64BIT=y CONFIG_ZONE_DMA_FLAG=1CONFIG_BOUNCE=yCONFIG_VIRT_TO_BUS=y
# CONFIG_KSM is not set CONFIG_DEFAULT_MMAP_MIN_ADDR=4096 CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
# CONFIG_MEMORY_FAILURE is not set
# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set CONFIG_X86_RESERVE_LOW_64K=yCONFIG_MTRR=y
# CONFIG_MTRR_SANITIZER is not set CONFIG_X86_PAT=y CONFIG_ARCH_USES_PG_UNCACHED=y
# CONFIG_EFI is not setCONFIG_SECCOMP=y
# CONFIG_CC_STACKPROTECTOR is not set
# CONFIG_HZ_100 is not setCONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not setCONFIG_HZ=250CONFIG_SCHED_HRTICK=y
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set CONFIG_PHYSICAL_START=0x1000000 CONFIG_RELOCATABLE=y CONFIG_PHYSICAL_ALIGN=0x1000000 CONFIG_COMPAT_VDSO=y
# CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
#
# Power management and ACPI options
#CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
# CONFIG_SUSPEND is not set
# CONFIG_HIBERNATION is not set
# CONFIG_PM_RUNTIME is not setCONFIG_ACPI=yCONFIG_ACPI_PROCFS=yCONFIG_ACPI_PROCFS_POWER=y
# CONFIG_ACPI_POWER_METER is not setCONFIG_ACPI_SYSFS_POWER=y
# CONFIG_ACPI_EC_DEBUGFS is not set
# CONFIG_ACPI_PROC_EVENT is not setCONFIG_ACPI_AC=yCONFIG_ACPI_BATTERY=yCONFIG_ACPI_BUTTON=yCONFIG_ACPI_VIDEO=yCONFIG_ACPI_FAN=yCONFIG_ACPI_DOCK=yCONFIG_ACPI_PROCESSOR=y
# CONFIG_ACPI_PROCESSOR_AGGREGATOR is not setCONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_CUSTOM_DSDT is not setCONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
# CONFIG_ACPI_PCI_SLOT is not setCONFIG_X86_PM_TIMER=yCONFIG_ACPI_CONTAINER=y
# CONFIG_ACPI_SBS is not set
# CONFIG_ACPI_HED is not set
# CONFIG_ACPI_APEI is not set
# CONFIG_SFI is not set
#
# CPU Frequency scaling
#CONFIG_CPU_FREQ=yCONFIG_CPU_FREQ_TABLE=y CONFIG_CPU_FREQ_DEBUG=y
# CONFIG_CPU_FREQ_STAT is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=y CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set
#
# CPUFreq processor drivers
#
# CONFIG_X86_PCC_CPUFREQ is not setCONFIG_X86_ACPI_CPUFREQ=yCONFIG_X86_POWERNOW_K8=yCONFIG_X86_SPEEDSTEP_CENTRINO=y
# CONFIG_X86_P4_CLOCKMOD is not set
#
# shared options # # CONFIG_X86_SPEEDSTEP_LIB is not set CONFIG_CPU_IDLE=y CONFIG_CPU_IDLE_GOV_LADDER=y CONFIG_CPU_IDLE_GOV_MENU=y # CONFIG_INTEL_IDLE is not set
#
# Memory power savings
#
# CONFIG_I7300_IDLE is not set
#
# Bus options (PCI etc.)
#CONFIG_PCI=yCONFIG_PCI_DIRECT=yCONFIG_PCI_MMCONFIG=yCONFIG_PCI_DOMAINS=y
# CONFIG_PCI_CNB20LE_QUIRK is not set
# CONFIG_DMAR is not set
# CONFIG_INTR_REMAP is not setCONFIG_PCIEPORTBUS=y
# CONFIG_HOTPLUG_PCI_PCIE is not setCONFIG_PCIEAER=y
# CONFIG_PCIE_ECRC is not set
# CONFIG_PCIEAER_INJECT is not setCONFIG_PCIEASPM=y
# CONFIG_PCIEASPM_DEBUG is not setCONFIG_ARCH_SUPPORTS_MSI=yCONFIG_PCI_MSI=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_STUB is not set
# CONFIG_HT_IRQ is not set
# CONFIG_PCI_IOV is not setCONFIG_PCI_IOAPIC=yCONFIG_ISA_DMA_API=yCONFIG_K8_NB=y
# CONFIG_PCCARD is not setCONFIG_HOTPLUG_PCI=y
# CONFIG_HOTPLUG_PCI_FAKE is not set
# CONFIG_HOTPLUG_PCI_ACPI is not set
# CONFIG_HOTPLUG_PCI_CPCI is not set
# CONFIG_HOTPLUG_PCI_SHPC is not set
#
# Executable file formats / Emulations
#CONFIG_BINFMT_ELF=yCONFIG_COMPAT_BINFMT_ELF=y
# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
# CONFIG_HAVE_AOUT is not setCONFIG_BINFMT_MISC=yCONFIG_IA32_EMULATION=y
# CONFIG_IA32_AOUT is not setCONFIG_COMPAT=yCONFIG_COMPAT_FOR_U64_ALIGNMENT=yCONFIG_SYSVIPC_COMPAT=yCONFIG_NET=y
#
# Networking options
#CONFIG_PACKET=yCONFIG_UNIX=yCONFIG_XFRM=y
# CONFIG_XFRM_USER is not set
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
# CONFIG_NET_KEY is not setCONFIG_INET=yCONFIG_IP_MULTICAST=y CONFIG_IP_ADVANCED_ROUTER=y CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set CONFIG_IP_FIB_HASH=y CONFIG_IP_MULTIPLE_TABLES=y CONFIG_IP_ROUTE_MULTIPATH=y CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set CONFIG_IP_MROUTE=y
# CONFIG_IP_MROUTE_MULTIPLE_TABLES is not set CONFIG_IP_PIMSM_V1=yCONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not setCONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set CONFIG_INET_TUNNEL=y CONFIG_INET_XFRM_MODE_TRANSPORT=y CONFIG_INET_XFRM_MODE_TUNNEL=y
# CONFIG_INET_XFRM_MODE_BEET is not set
# CONFIG_INET_LRO is not set
# CONFIG_INET_DIAG is not set
# CONFIG_TCP_CONG_ADVANCED is not set CONFIG_TCP_CONG_CUBIC=y CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not setCONFIG_IPV6=y
# CONFIG_IPV6_PRIVACY is not set
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
# CONFIG_INET6_IPCOMP is not set
# CONFIG_IPV6_MIP6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_INET6_XFRM_MODE_TRANSPORT is not set # CONFIG_INET6_XFRM_MODE_TUNNEL is not set
# CONFIG_INET6_XFRM_MODE_BEET is not set
# CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set CONFIG_IPV6_SIT=y
# CONFIG_IPV6_SIT_6RD is not set CONFIG_IPV6_NDISC_NODETYPE=y
# CONFIG_IPV6_TUNNEL is not set
# CONFIG_IPV6_MULTIPLE_TABLES is not set
# CONFIG_IPV6_MROUTE is not set
# CONFIG_NETLABEL is not set CONFIG_NETWORK_SECMARK=y
# CONFIG_NETWORK_PHY_TIMESTAMPING is not set CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
# CONFIG_NETFILTER_ADVANCED is not set
#
# Core Netfilter Configuration
#
# CONFIG_NETFILTER_NETLINK_LOG is not setCONFIG_NF_CONNTRACK=y
# CONFIG_NF_CONNTRACK_SECMARK is not setCONFIG_NF_CONNTRACK_FTP=y
# CONFIG_NF_CONNTRACK_IRC is not set
# CONFIG_NF_CONNTRACK_SIP is not set
# CONFIG_NF_CT_NETLINK is not setCONFIG_NETFILTER_XTABLES=y
#
# Xtables combined modules
#CONFIG_NETFILTER_XT_MARK=y
#
# Xtables targets
#
# CONFIG_NETFILTER_XT_TARGET_NFLOG is not setCONFIG_NETFILTER_XT_TARGET_SECMARK=y
# CONFIG_NETFILTER_XT_TARGET_TCPMSS is not set
#
# Xtables matches
#CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y
# CONFIG_NETFILTER_XT_MATCH_POLICY is not setCONFIG_NETFILTER_XT_MATCH_STATE=y
# CONFIG_IP_VS is not set
#
# IP: Netfilter Configuration
#CONFIG_NF_DEFRAG_IPV4=yCONFIG_NF_CONNTRACK_IPV4=yCONFIG_NF_CONNTRACK_PROC_COMPAT=yCONFIG_IP_NF_IPTABLES=yCONFIG_IP_NF_FILTER=yCONFIG_IP_NF_TARGET_REJECT=yCONFIG_IP_NF_TARGET_LOG=yCONFIG_IP_NF_TARGET_ULOG=yCONFIG_NF_NAT=yCONFIG_NF_NAT_NEEDED=yCONFIG_IP_NF_TARGET_MASQUERADE=yCONFIG_NF_NAT_FTP=y
# CONFIG_NF_NAT_IRC is not set
# CONFIG_NF_NAT_TFTP is not set
# CONFIG_NF_NAT_AMANDA is not set
# CONFIG_NF_NAT_PPTP is not set
# CONFIG_NF_NAT_H323 is not set
# CONFIG_NF_NAT_SIP is not setCONFIG_IP_NF_MANGLE=y
#
# IPv6: Netfilter Configuration
#CONFIG_NF_CONNTRACK_IPV6=yCONFIG_IP6_NF_IPTABLES=yCONFIG_IP6_NF_MATCH_IPV6HEADER=yCONFIG_IP6_NF_TARGET_LOG=yCONFIG_IP6_NF_FILTER=yCONFIG_IP6_NF_TARGET_REJECT=y
# CONFIG_IP6_NF_MANGLE is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_RDS is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_L2TP is not set
# CONFIG_BRIDGE is not set
# CONFIG_NET_DSA is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not setCONFIG_LLC=y
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_PHONET is not set
# CONFIG_IEEE802154 is not setCONFIG_NET_SCHED=y
#
# Queueing/Scheduling
#
# CONFIG_NET_SCH_CBQ is not set
# CONFIG_NET_SCH_HTB is not set
# CONFIG_NET_SCH_HFSC is not set
# CONFIG_NET_SCH_PRIO is not set
# CONFIG_NET_SCH_MULTIQ is not set
# CONFIG_NET_SCH_RED is not set
# CONFIG_NET_SCH_SFQ is not set
# CONFIG_NET_SCH_TEQL is not set
# CONFIG_NET_SCH_TBF is not set
# CONFIG_NET_SCH_GRED is not set
# CONFIG_NET_SCH_DSMARK is not set
# CONFIG_NET_SCH_NETEM is not set
# CONFIG_NET_SCH_DRR is not set
# CONFIG_NET_SCH_INGRESS is not set
#
# Classification
#CONFIG_NET_CLS=y
# CONFIG_NET_CLS_BASIC is not set
# CONFIG_NET_CLS_TCINDEX is not set
# CONFIG_NET_CLS_ROUTE4 is not set
# CONFIG_NET_CLS_FW is not set
# CONFIG_NET_CLS_U32 is not set
# CONFIG_NET_CLS_RSVP is not set
# CONFIG_NET_CLS_RSVP6 is not set
# CONFIG_NET_CLS_FLOW is not setCONFIG_NET_EMATCH=yCONFIG_NET_EMATCH_STACK=32
# CONFIG_NET_EMATCH_CMP is not set
# CONFIG_NET_EMATCH_NBYTE is not set
# CONFIG_NET_EMATCH_U32 is not set
# CONFIG_NET_EMATCH_META is not set
# CONFIG_NET_EMATCH_TEXT is not setCONFIG_NET_CLS_ACT=yCONFIG_NET_ACT_POLICE=y
# CONFIG_NET_ACT_GACT is not set
# CONFIG_NET_ACT_MIRRED is not set
# CONFIG_NET_ACT_IPT is not set
# CONFIG_NET_ACT_NAT is not set
# CONFIG_NET_ACT_PEDIT is not set
# CONFIG_NET_ACT_SIMP is not set
# CONFIG_NET_ACT_SKBEDIT is not setCONFIG_NET_SCH_FIFO=y
# CONFIG_DCB is not set
# CONFIG_DNS_RESOLVER is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NET_DROP_MONITOR is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not setCONFIG_FIB_RULES=yCONFIG_WIRELESS=y
# CONFIG_CFG80211 is not set
# CONFIG_LIB80211 is not set
#
# CFG80211 needs to be enabled for MAC80211
#
#
# Some wireless drivers require a rate control algorithm #
# CONFIG_WIMAX is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set
# CONFIG_CAIF is not set
#
# Device Drivers
#
#
# Generic Driver Options
#CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
# CONFIG_DEVTMPFS is not setCONFIG_STANDALONE=yCONFIG_PREVENT_FIRMWARE_BUILD=yCONFIG_FW_LOADER=yCONFIG_FIRMWARE_IN_KERNEL=yCONFIG_EXTRA_FIRMWARE=""
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_CONNECTOR is not set
# CONFIG_MTD is not set
# CONFIG_PARPORT is not setCONFIG_PNP=yCONFIG_PNP_DEBUG_MESSAGES=y
#
# Protocols
#CONFIG_PNPACPI=yCONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
# CONFIG_BLK_DEV_LOOP is not set
#
# DRBD disabled because PROC_FS, INET or CONNECTOR not selected #
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not setCONFIG_BLK_DEV_RAM=yCONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=16384
# CONFIG_BLK_DEV_XIP is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_BLK_DEV_HD is not setCONFIG_MISC_DEVICES=y
# CONFIG_AD525X_DPOT is not set
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_ICS932S401 is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_CS5535_MFGPT is not set
# CONFIG_HP_ILO is not set
# CONFIG_ISL29003 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_SENSORS_BH1780 is not set
# CONFIG_HMC6352 is not set
# CONFIG_DS1682 is not set
# CONFIG_VMWARE_BALLOON is not set
# CONFIG_BMP085 is not set
# CONFIG_C2PORT is not set
#
# EEPROM support
#
# CONFIG_EEPROM_AT24 is not set
# CONFIG_EEPROM_LEGACY is not set
# CONFIG_EEPROM_MAX6875 is not set
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_CB710_CORE is not setCONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#CONFIG_SCSI_MOD=y
# CONFIG_RAID_ATTRS is not setCONFIG_SCSI=yCONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not setCONFIG_SCSI_NETLINK=y
# CONFIG_SCSI_PROC_FS is not set
#
# SCSI support type (disk, tape, CD-ROM)
#CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not setCONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not setCONFIG_CHR_DEV_SG=y
# CONFIG_CHR_DEV_SCH is not setCONFIG_SCSI_MULTI_LUN=y
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not setCONFIG_SCSI_FC_ATTRS=y
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not setCONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_ISCSI_BOOT_SYSFS is not set
# CONFIG_SCSI_CXGB3_ISCSI is not set
# CONFIG_SCSI_BNX2_ISCSI is not set
# CONFIG_BE2ISCSI is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_HPSA is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_3W_SAS is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_MVSAS is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_MPT2SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_VMWARE_PVSCSI is not set
# CONFIG_LIBFC is not set
# CONFIG_LIBFCOE is not set
# CONFIG_FCOE is not set
# CONFIG_FCOE_FNIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_PMCRAID is not set
# CONFIG_SCSI_PM8001 is not set
# CONFIG_SCSI_SRP is not set
# CONFIG_SCSI_BFA_FC is not set
# CONFIG_SCSI_DH is not set
# CONFIG_SCSI_OSD_INITIATOR is not setCONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not setCONFIG_ATA_VERBOSE_ERROR=yCONFIG_ATA_ACPI=yCONFIG_SATA_PMP=y
#
# Controllers with non-SFF native interface
#CONFIG_SATA_AHCI=y
# CONFIG_SATA_AHCI_PLATFORM is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_SATA_SIL24 is not setCONFIG_ATA_SFF=y
#
# SFF controllers with custom DMA interface
#
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_SX4 is not setCONFIG_ATA_BMDMA=y
#
# SATA SFF controllers with BMDMA
#CONFIG_ATA_PIIX=y
# CONFIG_SATA_MV is not set
# CONFIG_SATA_NV is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_SVW is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
#
# PATA SFF controllers with BMDMA
#
# CONFIG_PATA_ALI is not setCONFIG_PATA_AMD=y
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_ATP867X is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RDC is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SCH is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_TOSHIBA is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
#
# PIO-only SFF controllers
#
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_RZ1000 is not set
#
# Generic fallback / legacy drivers
#
# CONFIG_PATA_ACPI is not set
# CONFIG_ATA_GENERIC is not set
# CONFIG_PATA_LEGACY is not setCONFIG_MD=yCONFIG_BLK_DEV_MD=yCONFIG_MD_AUTODETECT=yCONFIG_MD_LINEAR=yCONFIG_MD_RAID0=y
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID456 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_MD_FAULTY is not setCONFIG_BLK_DEV_DM=y
# CONFIG_DM_DEBUG is not set
# CONFIG_DM_CRYPT is not setCONFIG_DM_SNAPSHOT=yCONFIG_DM_MIRROR=y
# CONFIG_DM_LOG_USERSPACE is not setCONFIG_DM_ZERO=y
# CONFIG_DM_MULTIPATH is not set
# CONFIG_DM_DELAY is not set
# CONFIG_DM_UEVENT is not set
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#
#
# You can enable one or both FireWire driver stacks. #
#
# The newer stack is recommended.
#
# CONFIG_FIREWIRE is not set
# CONFIG_IEEE1394 is not set
# CONFIG_FIREWIRE_NOSY is not set
# CONFIG_I2O is not set
# CONFIG_MACINTOSH_DRIVERS is not set CONFIG_NETDEVICES=y
# CONFIG_IFB is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_VETH is not set
# CONFIG_NET_SB1000 is not set
# CONFIG_ARCNET is not set
# CONFIG_PHYLIB is not set CONFIG_NET_ETHERNET=y
# CONFIG_MII is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set CONFIG_NET_VENDOR_3COM=y
# CONFIG_VORTEX is not set
# CONFIG_TYPHOON is not set
# CONFIG_ETHOC is not set
# CONFIG_DNET is not set CONFIG_NET_TULIP=y
# CONFIG_DE2104X is not set
# CONFIG_TULIP is not set
# CONFIG_DE4X5 is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_DM9102 is not set
# CONFIG_ULI526X is not set
# CONFIG_HP100 is not set
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
# CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set # CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set # CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_KSZ884X_PCI is not set
# CONFIG_B44 is not setCONFIG_FORCEDETH=y
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_R6040 is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SMSC9420 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_KS8851_MLL is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_SC92031 is not set
# CONFIG_ATL2 is not set CONFIG_NETDEV_1000=y
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not setCONFIG_E1000=yCONFIG_E1000E=y
# CONFIG_IP1000 is not setCONFIG_IGB=y
# CONFIG_IGBVF is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_VIA_VELOCITY is not set
# CONFIG_TIGON3 is not set
# CONFIG_BNX2 is not set
# CONFIG_CNIC is not set
# CONFIG_QLA3XXX is not set
# CONFIG_ATL1 is not set
# CONFIG_ATL1E is not set
# CONFIG_ATL1C is not set
# CONFIG_JME is not set CONFIG_NETDEV_10000=y
# CONFIG_CHELSIO_T1 is not set CONFIG_CHELSIO_T3_DEPENDS=y
# CONFIG_CHELSIO_T3 is not set CONFIG_CHELSIO_T4_DEPENDS=y
# CONFIG_CHELSIO_T4 is not set CONFIG_CHELSIO_T4VF_DEPENDS=y
# CONFIG_CHELSIO_T4VF is not set
# CONFIG_ENIC is not set
# CONFIG_IXGBE is not set
# CONFIG_IXGBEVF is not set
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
# CONFIG_VXGE is not set
# CONFIG_MYRI10GE is not set
# CONFIG_NETXEN_NIC is not set
# CONFIG_NIU is not set
# CONFIG_MLX4_EN is not set
# CONFIG_MLX4_CORE is not set
# CONFIG_TEHUTI is not set
# CONFIG_BNX2X is not set
# CONFIG_QLCNIC is not set
# CONFIG_QLGE is not set
# CONFIG_SFC is not set
# CONFIG_BE2NET is not setCONFIG_TR=y
# CONFIG_IBMOL is not set
# CONFIG_3C359 is not set
# CONFIG_TMS380TR is not setCONFIG_WLAN=y
# CONFIG_AIRO is not set
# CONFIG_ATMEL is not set
# CONFIG_PRISM54 is not set
# CONFIG_USB_ZD1201 is not set
# CONFIG_HOSTAP is not set
#
# Enable WiMAX (Networking options) to see the WiMAX drivers #
#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_IPHETH is not set
# CONFIG_WAN is not set
#
# CAIF transport drivers
#CONFIG_FDDI=y
# CONFIG_DEFXX is not set
# CONFIG_SKFP is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_VMXNET3 is not set
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set
#
# Input device support
#CONFIG_INPUT=yCONFIG_INPUT_FF_MEMLESS=y
# CONFIG_INPUT_POLLDEV is not set
# CONFIG_INPUT_SPARSEKMAP is not set
#
# Userland interfaces
#CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not setCONFIG_INPUT_MOUSEDEV_SCREEN_X=1024CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not setCONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADP5588 is not setCONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_QT2160 is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_TCA6416 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_MCS is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not setCONFIG_INPUT_MOUSE=yCONFIG_MOUSE_PS2=yCONFIG_MOUSE_PS2_ALPS=yCONFIG_MOUSE_PS2_LOGIPS2PP=yCONFIG_MOUSE_PS2_SYNAPTICS=yCONFIG_MOUSE_PS2_LIFEBOOK=yCONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_ELANTECH is not set
# CONFIG_MOUSE_PS2_SENTELIC is not set
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_MOUSE_SYNAPTICS_I2C is not setCONFIG_INPUT_JOYSTICK=y
# CONFIG_JOYSTICK_ANALOG is not set
# CONFIG_JOYSTICK_A3D is not set
# CONFIG_JOYSTICK_ADI is not set
# CONFIG_JOYSTICK_COBRA is not set
# CONFIG_JOYSTICK_GF2K is not set
# CONFIG_JOYSTICK_GRIP is not set
# CONFIG_JOYSTICK_GRIP_MP is not set
# CONFIG_JOYSTICK_GUILLEMOT is not set
# CONFIG_JOYSTICK_INTERACT is not set
# CONFIG_JOYSTICK_SIDEWINDER is not set
# CONFIG_JOYSTICK_TMDC is not set
# CONFIG_JOYSTICK_IFORCE is not set
# CONFIG_JOYSTICK_WARRIOR is not set
# CONFIG_JOYSTICK_MAGELLAN is not set
# CONFIG_JOYSTICK_SPACEORB is not set
# CONFIG_JOYSTICK_SPACEBALL is not set
# CONFIG_JOYSTICK_STINGER is not set
# CONFIG_JOYSTICK_TWIDJOY is not set
# CONFIG_JOYSTICK_ZHENHUA is not set
# CONFIG_JOYSTICK_JOYDUMP is not set
# CONFIG_JOYSTICK_XPAD is not set
# CONFIG_INPUT_TABLET is not setCONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_TOUCHSCREEN_DYNAPRO is not set
# CONFIG_TOUCHSCREEN_HAMPSHIRE is not set
# CONFIG_TOUCHSCREEN_EETI is not set
# CONFIG_TOUCHSCREEN_FUJITSU is not set
# CONFIG_TOUCHSCREEN_GUNZE is not set
# CONFIG_TOUCHSCREEN_ELO is not set
# CONFIG_TOUCHSCREEN_WACOM_W8001 is not set
# CONFIG_TOUCHSCREEN_MCS5000 is not set
# CONFIG_TOUCHSCREEN_MTOUCH is not set
# CONFIG_TOUCHSCREEN_INEXIO is not set
# CONFIG_TOUCHSCREEN_MK712 is not set
# CONFIG_TOUCHSCREEN_PENMOUNT is not set
# CONFIG_TOUCHSCREEN_QT602240 is not set
# CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set
# CONFIG_TOUCHSCREEN_TOUCHWIN is not set
# CONFIG_TOUCHSCREEN_WM97XX is not set
# CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set
# CONFIG_TOUCHSCREEN_TOUCHIT213 is not set
# CONFIG_TOUCHSCREEN_TSC2007 is not set
# CONFIG_TOUCHSCREEN_TPS6507X is not setCONFIG_INPUT_MISC=y
# CONFIG_INPUT_AD714X is not set
# CONFIG_INPUT_PCSPKR is not set
# CONFIG_INPUT_ATLAS_BTNS is not set
# CONFIG_INPUT_ATI_REMOTE is not set
# CONFIG_INPUT_ATI_REMOTE2 is not set
# CONFIG_INPUT_KEYSPAN_REMOTE is not set
# CONFIG_INPUT_POWERMATE is not set
# CONFIG_INPUT_YEALINK is not set
# CONFIG_INPUT_CM109 is not set
# CONFIG_INPUT_UINPUT is not set
# CONFIG_INPUT_WINBOND_CIR is not set
# CONFIG_INPUT_PCF8574 is not set
# CONFIG_INPUT_ADXL34X is not set
#
# Hardware I/O ports
#CONFIG_SERIO=yCONFIG_SERIO_I8042=yCONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not setCONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_SERIO_ALTERA_PS2 is not set
# CONFIG_GAMEPORT is not set
#
# Character devices
#CONFIG_VT=yCONFIG_CONSOLE_TRANSLATIONS=yCONFIG_VT_CONSOLE=yCONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not setCONFIG_DEVKMEM=yCONFIG_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
# CONFIG_ROCKETPORT is not set
# CONFIG_CYCLADES is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_ISI is not set
# CONFIG_SYNCLINK is not set
# CONFIG_SYNCLINKMP is not set
# CONFIG_SYNCLINK_GT is not set
# CONFIG_N_HDLC is not set
# CONFIG_N_GSM is not set
# CONFIG_RISCOM8 is not set
# CONFIG_SPECIALIX is not setCONFIG_STALDRV=y
# CONFIG_STALLION is not set
# CONFIG_ISTALLION is not set
# CONFIG_NOZOMI is not set
#
# Serial drivers
#CONFIG_SERIAL_8250=yCONFIG_SERIAL_8250_CONSOLE=yCONFIG_FIX_EARLYCON_MEM=yCONFIG_SERIAL_8250_PCI=yCONFIG_SERIAL_8250_PNP=yCONFIG_SERIAL_8250_NR_UARTS=32CONFIG_SERIAL_8250_RUNTIME_UARTS=4CONFIG_SERIAL_8250_EXTENDED=yCONFIG_SERIAL_8250_MANY_PORTS=yCONFIG_SERIAL_8250_SHARE_IRQ=yCONFIG_SERIAL_8250_DETECT_IRQ=yCONFIG_SERIAL_8250_RSA=y
#
# Non-8250 serial port support
#
# CONFIG_SERIAL_MFD_HSU is not setCONFIG_SERIAL_CORE=yCONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
# CONFIG_SERIAL_TIMBERDALE is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not setCONFIG_UNIX98_PTYS=y
# CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set
# CONFIG_LEGACY_PTYS is not set
# CONFIG_IPMI_HANDLER is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not setCONFIG_RTC=y
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not setCONFIG_HPET=y
# CONFIG_HPET_MMAP is not set
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not setCONFIG_DEVPORT=y
# CONFIG_RAMOOPS is not setCONFIG_I2C=yCONFIG_I2C_BOARDINFO=yCONFIG_I2C_COMPAT=y
# CONFIG_I2C_CHARDEV is not set
# CONFIG_I2C_MUX is not setCONFIG_I2C_HELPER_AUTO=yCONFIG_I2C_ALGOBIT=y
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_ISCH is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
#
# ACPI drivers
#
# CONFIG_I2C_SCMI is not set
#
# I2C system bus drivers (mostly embedded / system-on-chip) #
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_SIMTEC is not set
# CONFIG_I2C_XILINX is not set
#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set
#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_SPI is not set
#
# PPS support
#
# CONFIG_PPS is not setCONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
# CONFIG_GPIOLIB is not set
# CONFIG_W1 is not setCONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_TEST_POWER is not set
# CONFIG_BATTERY_DS2760 is not set
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_BQ27x00 is not set
# CONFIG_BATTERY_MAX17040 is not setCONFIG_HWMON=y
# CONFIG_HWMON_VID is not set
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Native drivers
#
# CONFIG_SENSORS_ABITUGURU is not set
# CONFIG_SENSORS_ABITUGURU3 is not set
# CONFIG_SENSORS_AD7414 is not set
# CONFIG_SENSORS_AD7418 is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1029 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ADT7411 is not set
# CONFIG_SENSORS_ADT7462 is not set
# CONFIG_SENSORS_ADT7470 is not set
# CONFIG_SENSORS_ADT7475 is not set
# CONFIG_SENSORS_ASC7621 is not set
# CONFIG_SENSORS_K8TEMP is not set
# CONFIG_SENSORS_K10TEMP is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_I5K_AMB is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_F71882FG is not set
# CONFIG_SENSORS_F75375S is not set
# CONFIG_SENSORS_FSCHMD is not set
# CONFIG_SENSORS_G760A is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_CORETEMP is not set
# CONFIG_SENSORS_PKGTEMP is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_JC42 is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM73 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_LM93 is not set
# CONFIG_SENSORS_LTC4215 is not set
# CONFIG_SENSORS_LTC4245 is not set
# CONFIG_SENSORS_LM95241 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_MAX6650 is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_PC87427 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_SMM665 is not set
# CONFIG_SENSORS_DME1737 is not set
# CONFIG_SENSORS_EMC1403 is not set
# CONFIG_SENSORS_EMC2103 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_ADS7828 is not set
# CONFIG_SENSORS_AMC6821 is not set
# CONFIG_SENSORS_THMC50 is not set
# CONFIG_SENSORS_TMP102 is not set
# CONFIG_SENSORS_TMP401 is not set
# CONFIG_SENSORS_TMP421 is not set
# CONFIG_SENSORS_VIA_CPUTEMP is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83L786NG is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_SENSORS_LIS3_I2C is not set
# CONFIG_SENSORS_APPLESMC is not set
#
# ACPI drivers
#
# CONFIG_SENSORS_ATK0110 is not set
# CONFIG_SENSORS_LIS3LV02D is not setCONFIG_THERMAL=y
# CONFIG_THERMAL_HWMON is not setCONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not set
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
# CONFIG_ALIM1535_WDT is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_F71808E_WDT is not set
# CONFIG_SC520_WDT is not set
# CONFIG_SBC_FITPC2_WATCHDOG is not set
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
# CONFIG_IBMASR is not set
# CONFIG_WAFER_WDT is not set
# CONFIG_I6300ESB_WDT is not set
# CONFIG_ITCO_WDT is not set
# CONFIG_IT8712F_WDT is not set
# CONFIG_IT87_WDT is not set
# CONFIG_HP_WATCHDOG is not set
# CONFIG_SC1200_WDT is not set
# CONFIG_PC87413_WDT is not set
# CONFIG_60XX_WDT is not set
# CONFIG_SBC8360_WDT is not set
# CONFIG_CPU5_WDT is not set
# CONFIG_SMSC_SCH311X_WDT is not set
# CONFIG_SMSC37B787_WDT is not set
# CONFIG_W83627HF_WDT is not set
# CONFIG_W83697HF_WDT is not set
# CONFIG_W83697UG_WDT is not set
# CONFIG_W83877F_WDT is not set
# CONFIG_W83977F_WDT is not set
# CONFIG_MACHZ_WDT is not set
# CONFIG_SBC_EPX_C3_WATCHDOG is not set
#
# PCI-based Watchdog Cards
#
# CONFIG_PCIPCWATCHDOG is not set
# CONFIG_WDTPCI is not set
#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not setCONFIG_SSB_POSSIBLE=y
#
# Sonics Silicon Backplane
#
# CONFIG_SSB is not setCONFIG_MFD_SUPPORT=y
# CONFIG_MFD_CORE is not set
# CONFIG_MFD_88PM860X is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_TPS6507X is not set
# CONFIG_TWL4030_CORE is not set
# CONFIG_MFD_STMPE is not set
# CONFIG_MFD_TC35892 is not set
# CONFIG_MFD_TMIO is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_MAX8925 is not set
# CONFIG_MFD_MAX8998 is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_WM8994 is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_ABX500_CORE is not set
# CONFIG_LPC_SCH is not set
# CONFIG_MFD_RDC321X is not set
# CONFIG_MFD_JANZ_CMODIO is not set
# CONFIG_REGULATOR is not set
# CONFIG_MEDIA_SUPPORT is not set
#
# Graphics support
#CONFIG_AGP=yCONFIG_AGP_AMD64=yCONFIG_AGP_INTEL=y
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_VIA is not setCONFIG_VGA_ARB=yCONFIG_VGA_ARB_MAX_GPUS=16
# CONFIG_VGA_SWITCHEROO is not setCONFIG_DRM=yCONFIG_DRM_KMS_HELPER=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not setCONFIG_DRM_I915=y
# CONFIG_DRM_I915_KMS is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
# CONFIG_VGASTATE is not setCONFIG_VIDEO_OUTPUT_CONTROL=yCONFIG_FB=yCONFIG_FIRMWARE_EDID=y
# CONFIG_FB_DDC is not setCONFIG_FB_BOOT_VESA_SUPPORT=yCONFIG_FB_CFB_FILLRECT=yCONFIG_FB_CFB_COPYAREA=yCONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
# CONFIG_FB_SYS_FILLRECT is not set
# CONFIG_FB_SYS_COPYAREA is not set
# CONFIG_FB_SYS_IMAGEBLIT is not set
# CONFIG_FB_FOREIGN_ENDIAN is not set
# CONFIG_FB_SYS_FOPS is not set
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not setCONFIG_FB_MODE_HELPERS=yCONFIG_FB_TILEBLITTING=y
#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not setCONFIG_FB_VESA=y
# CONFIG_FB_N411 is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_VIA is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
# CONFIG_FB_BROADSHEET is not setCONFIG_BACKLIGHT_LCD_SUPPORT=y
# CONFIG_LCD_CLASS_DEVICE is not setCONFIG_BACKLIGHT_CLASS_DEVICE=yCONFIG_BACKLIGHT_GENERIC=y
# CONFIG_BACKLIGHT_PROGEAR is not set
# CONFIG_BACKLIGHT_MBP_NVIDIA is not set
# CONFIG_BACKLIGHT_SAHARA is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
#
# Display device support
#CONFIG_DISPLAY_SUPPORT=y
#
# Display hardware drivers
#
#
# Console display driver support
#CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set # CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set # CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=yCONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set CONFIG_LOGO_LINUX_CLUT224=yCONFIG_SOUND=yCONFIG_SOUND_OSS_CORE=y CONFIG_SOUND_OSS_CORE_PRECLAIM=yCONFIG_SND=yCONFIG_SND_TIMER=yCONFIG_SND_PCM=yCONFIG_SND_SEQUENCER=y
# CONFIG_SND_SEQ_DUMMY is not set CONFIG_SND_OSSEMUL=yCONFIG_SND_MIXER_OSS=yCONFIG_SND_PCM_OSS=y CONFIG_SND_PCM_OSS_PLUGINS=y CONFIG_SND_SEQUENCER_OSS=y CONFIG_SND_HRTIMER=y CONFIG_SND_SEQ_HRTIMER_DEFAULT=y CONFIG_SND_RTCTIMER=y CONFIG_SND_DYNAMIC_MINORS=y CONFIG_SND_SUPPORT_OLD_API=y
# CONFIG_SND_VERBOSE_PROCFS is not set
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set CONFIG_SND_VMASTER=yCONFIG_SND_DMA_SGBUF=y
# CONFIG_SND_RAWMIDI_SEQ is not set
# CONFIG_SND_OPL3_LIB_SEQ is not set
# CONFIG_SND_OPL4_LIB_SEQ is not set
# CONFIG_SND_SBAWE_SEQ is not set
# CONFIG_SND_EMU10K1_SEQ is not set CONFIG_SND_AC97_CODEC=yCONFIG_SND_DRIVERS=y
# CONFIG_SND_PCSP is not set
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
# CONFIG_SND_AC97_POWER_SAVE is not set CONFIG_SND_PCI=y
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ASIHPI is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AW2 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_OXYGEN is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS5530 is not set
# CONFIG_SND_CS5535AUDIO is not set
# CONFIG_SND_CTXFI is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
# CONFIG_SND_INDIGOIOX is not set
# CONFIG_SND_INDIGODJX is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set CONFIG_SND_HDA_INTEL=y
# CONFIG_SND_HDA_HWDEP is not set CONFIG_SND_HDA_INPUT_BEEP=y CONFIG_SND_HDA_INPUT_BEEP_MODE=1
# CONFIG_SND_HDA_INPUT_JACK is not set
# CONFIG_SND_HDA_PATCH_LOADER is not set CONFIG_SND_HDA_CODEC_REALTEK=y CONFIG_SND_HDA_CODEC_ANALOG=y CONFIG_SND_HDA_CODEC_SIGMATEL=y CONFIG_SND_HDA_CODEC_VIA=y CONFIG_SND_HDA_CODEC_ATIHDMI=y
# CONFIG_SND_HDA_CODEC_NVHDMI is not set CONFIG_SND_HDA_CODEC_INTELHDMI=y CONFIG_SND_HDA_ELD=y CONFIG_SND_HDA_CODEC_CIRRUS=y CONFIG_SND_HDA_CODEC_CONEXANT=y CONFIG_SND_HDA_CODEC_CA0110=y CONFIG_SND_HDA_CODEC_CMEDIA=y CONFIG_SND_HDA_CODEC_SI3054=y CONFIG_SND_HDA_GENERIC=y
# CONFIG_SND_HDA_POWER_SAVE is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_HIFIER is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set CONFIG_SND_INTEL8X0=y
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_LX6464ES is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VIRTUOSO is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set CONFIG_SND_USB=y
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_UA101 is not set
# CONFIG_SND_USB_USX2Y is not set
# CONFIG_SND_USB_CAIAQ is not set
# CONFIG_SND_USB_US122L is not set
# CONFIG_SND_SOC is not set
# CONFIG_SOUND_PRIME is not set CONFIG_AC97_BUS=yCONFIG_HID_SUPPORT=yCONFIG_HID=y
# CONFIG_HIDRAW is not set
#
# USB Input Devices
#CONFIG_USB_HID=yCONFIG_HID_PID=yCONFIG_USB_HIDDEV=y
#
# Special HID drivers
#
# CONFIG_HID_3M_PCT is not setCONFIG_HID_A4TECH=y
# CONFIG_HID_ACRUX_FF is not setCONFIG_HID_APPLE=yCONFIG_HID_BELKIN=y
# CONFIG_HID_CANDO is not setCONFIG_HID_CHERRY=yCONFIG_HID_CHICONY=y
# CONFIG_HID_PRODIKEYS is not setCONFIG_HID_CYPRESS=yCONFIG_HID_DRAGONRISE=y
# CONFIG_DRAGONRISE_FF is not set
# CONFIG_HID_EGALAX is not setCONFIG_HID_EZKEY=yCONFIG_HID_KYE=yCONFIG_HID_GYRATION=yCONFIG_HID_TWINHAN=yCONFIG_HID_KENSINGTON=yCONFIG_HID_LOGITECH=yCONFIG_LOGITECH_FF=y
# CONFIG_LOGIRUMBLEPAD2_FF is not set
# CONFIG_LOGIG940_FF is not setCONFIG_HID_MICROSOFT=y
# CONFIG_HID_MOSART is not setCONFIG_HID_MONTEREY=yCONFIG_HID_NTRIG=yCONFIG_HID_ORTEK=yCONFIG_HID_PANTHERLORD=y
# CONFIG_PANTHERLORD_FF is not setCONFIG_HID_PETALYNX=y
# CONFIG_HID_PICOLCD is not set
# CONFIG_HID_QUANTA is not set
# CONFIG_HID_ROCCAT is not set
# CONFIG_HID_ROCCAT_KONE is not setCONFIG_HID_SAMSUNG=yCONFIG_HID_SONY=y
# CONFIG_HID_STANTUM is not setCONFIG_HID_SUNPLUS=yCONFIG_HID_GREENASIA=y
# CONFIG_GREENASIA_FF is not setCONFIG_HID_SMARTJOYPLUS=y
# CONFIG_SMARTJOYPLUS_FF is not setCONFIG_HID_TOPSEED=yCONFIG_HID_THRUSTMASTER=yCONFIG_THRUSTMASTER_FF=yCONFIG_HID_ZEROPLUS=y
# CONFIG_ZEROPLUS_FF is not set
# CONFIG_HID_ZYDACRON is not setCONFIG_USB_SUPPORT=yCONFIG_USB_ARCH_HAS_HCD=yCONFIG_USB_ARCH_HAS_OHCI=yCONFIG_USB_ARCH_HAS_EHCI=yCONFIG_USB=y
# CONFIG_USB_DEBUG is not setCONFIG_USB_ANNOUNCE_NEW_DEVICES=y
#
# Miscellaneous USB options
#
# CONFIG_USB_DEVICEFS is not set
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not setCONFIG_USB_MON=y
# CONFIG_USB_WUSB is not set
# CONFIG_USB_WUSB_CBAF is not set
#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
# CONFIG_USB_XHCI_HCD is not setCONFIG_USB_EHCI_HCD=yCONFIG_USB_EHCI_ROOT_HUB_TT=y
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1760_HCD is not set
# CONFIG_USB_ISP1362_HCD is not set
# CONFIG_USB_OHCI_HCD is not setCONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_WHCI_HCD is not set
# CONFIG_USB_HWA_HCD is not set
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not setCONFIG_USB_PRINTER=y
# CONFIG_USB_WDM is not set
# CONFIG_USB_TMC is not set
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may #
#
# also be needed; see USB_STORAGE Help for more info # CONFIG_USB_STORAGE=y # CONFIG_USB_STORAGE_DEBUG is not set # CONFIG_USB_STORAGE_DATAFAB is not set # CONFIG_USB_STORAGE_FREECOM is not set # CONFIG_USB_STORAGE_ISD200 is not set # CONFIG_USB_STORAGE_USBAT is not set # CONFIG_USB_STORAGE_SDDR09 is not set # CONFIG_USB_STORAGE_SDDR55 is not set # CONFIG_USB_STORAGE_JUMPSHOT is not set # CONFIG_USB_STORAGE_ALAUDA is not set # CONFIG_USB_STORAGE_ONETOUCH is not set # CONFIG_USB_STORAGE_KARMA is not set # CONFIG_USB_STORAGE_CYPRESS_ATACB is not set # CONFIG_USB_LIBUSUAL is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
#
# USB port drivers
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_ISIGHTFW is not set
# CONFIG_USB_GADGET is not set
#
# OTG and related infrastructure
#
# CONFIG_NOP_USB_XCEIV is not set
# CONFIG_UWB is not set
# CONFIG_MMC is not set
# CONFIG_MEMSTICK is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not setCONFIG_EDAC=y
#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not setCONFIG_EDAC_DECODE_MCE=yCONFIG_EDAC_MM_EDAC=y
# CONFIG_EDAC_AMD64 is not set
# CONFIG_EDAC_E752X is not set
# CONFIG_EDAC_I82975X is not set
# CONFIG_EDAC_I3000 is not set
# CONFIG_EDAC_I3200 is not set
# CONFIG_EDAC_X38 is not set
# CONFIG_EDAC_I5400 is not set
# CONFIG_EDAC_I7CORE is not set
# CONFIG_EDAC_I5000 is not set
# CONFIG_EDAC_I5100 is not set
# CONFIG_RTC_CLASS is not set
# CONFIG_DMADEVICES is not set
# CONFIG_AUXDISPLAY is not set
# CONFIG_UIO is not set
# CONFIG_STAGING is not setCONFIG_X86_PLATFORM_DEVICES=y
# CONFIG_ASUS_LAPTOP is not set
# CONFIG_DELL_WMI is not set
# CONFIG_FUJITSU_LAPTOP is not set
# CONFIG_HP_WMI is not set
# CONFIG_PANASONIC_LAPTOP is not set
# CONFIG_THINKPAD_ACPI is not set
# CONFIG_INTEL_MENLOW is not set
# CONFIG_EEEPC_LAPTOP is not set
# CONFIG_EEEPC_WMI is not setCONFIG_ACPI_WMI=y
# CONFIG_MSI_WMI is not set
# CONFIG_ACPI_ASUS is not set
# CONFIG_TOPSTAR_LAPTOP is not set
# CONFIG_TOSHIBA_BT_RFKILL is not set
# CONFIG_ACPI_CMPC is not set
# CONFIG_INTEL_IPS is not set
#
# Firmware Drivers
#
# CONFIG_EDD is not setCONFIG_FIRMWARE_MEMMAP=y
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not setCONFIG_DMIID=y
# CONFIG_ISCSI_IBFT_FIND is not set
#
# File systems
#CONFIG_EXT2_FS=yCONFIG_EXT2_FS_XATTR=yCONFIG_EXT2_FS_POSIX_ACL=yCONFIG_EXT2_FS_SECURITY=y
# CONFIG_EXT2_FS_XIP is not setCONFIG_EXT3_FS=y
# CONFIG_EXT3_DEFAULTS_TO_ORDERED is not setCONFIG_EXT3_FS_XATTR=yCONFIG_EXT3_FS_POSIX_ACL=y
# CONFIG_EXT3_FS_SECURITY is not set
# CONFIG_EXT4_FS is not setCONFIG_JBD=y
# CONFIG_JBD_DEBUG is not setCONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not setCONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not setCONFIG_BTRFS_FS=yCONFIG_BTRFS_FS_POSIX_ACL=y
# CONFIG_NILFS2_FS is not setCONFIG_FILE_LOCKING=yCONFIG_FSNOTIFY=yCONFIG_DNOTIFY=yCONFIG_INOTIFY_USER=y
# CONFIG_FANOTIFY is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not setCONFIG_AUTOFS4_FS=y
# CONFIG_FUSE_FS is not setCONFIG_GENERIC_ACL=y
#
# Caches
#
# CONFIG_FSCACHE is not set
#
# CD-ROM/DVD Filesystems
#CONFIG_ISO9660_FS=yCONFIG_JOLIET=yCONFIG_ZISOFS=y
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#CONFIG_FAT_FS=yCONFIG_MSDOS_FS=yCONFIG_VFAT_FS=yCONFIG_FAT_DEFAULT_CODEPAGE=437CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#CONFIG_PROC_FS=yCONFIG_PROC_KCORE=yCONFIG_PROC_SYSCTL=yCONFIG_PROC_PAGE_MONITOR=yCONFIG_SYSFS=yCONFIG_TMPFS=yCONFIG_TMPFS_POSIX_ACL=yCONFIG_HUGETLBFS=yCONFIG_HUGETLB_PAGE=y
# CONFIG_CONFIGFS_FS is not set
# CONFIG_MISC_FILESYSTEMS is not setCONFIG_NETWORK_FILESYSTEMS=y
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_SMB_FS is not set
# CONFIG_CEPH_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not setCONFIG_OSF_PARTITION=yCONFIG_AMIGA_PARTITION=y
# CONFIG_ATARI_PARTITION is not setCONFIG_MAC_PARTITION=yCONFIG_MSDOS_PARTITION=yCONFIG_BSD_DISKLABEL=yCONFIG_MINIX_SUBPARTITION=yCONFIG_SOLARIS_X86_PARTITION=yCONFIG_UNIXWARE_DISKLABEL=y
# CONFIG_LDM_PARTITION is not setCONFIG_SGI_PARTITION=y
# CONFIG_ULTRIX_PARTITION is not setCONFIG_SUN_PARTITION=y
# CONFIG_KARMA_PARTITION is not setCONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not setCONFIG_NLS=yCONFIG_NLS_DEFAULT="utf8"CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not setCONFIG_NLS_ASCII=yCONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not setCONFIG_NLS_UTF8=y
# CONFIG_DLM is not set
#
# Kernel hacking
#CONFIG_TRACE_IRQFLAGS_SUPPORT=yCONFIG_PRINTK_TIME=y
# CONFIG_ENABLE_WARN_DEPRECATED is not set
# CONFIG_ENABLE_MUST_CHECK is not setCONFIG_FRAME_WARN=2048CONFIG_MAGIC_SYSRQ=y
# CONFIG_STRIP_ASM_SYMS is not setCONFIG_UNUSED_SYMBOLS=yCONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not setCONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
# CONFIG_LOCKUP_DETECTOR is not set
# CONFIG_HARDLOCKUP_DETECTOR is not set
# CONFIG_DETECT_HUNG_TASK is not setCONFIG_SCHED_DEBUG=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_TIMER_STATS is not set
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
# CONFIG_DEBUG_KMEMLEAK is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not setCONFIG_STACKTRACE=y
# CONFIG_DEBUG_KOBJECT is not setCONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_VIRTUAL is not set
# CONFIG_DEBUG_WRITECOUNT is not setCONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
# CONFIG_DEBUG_CREDENTIALS is not setCONFIG_ARCH_WANT_FRAME_POINTERS=yCONFIG_FRAME_POINTER=y
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
# CONFIG_LKDTM is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not setCONFIG_SYSCTL_SYSCALL_CHECK=y
# CONFIG_DEBUG_PAGEALLOC is not setCONFIG_USER_STACKTRACE_SUPPORT=yCONFIG_NOP_TRACER=yCONFIG_HAVE_FUNCTION_TRACER=yCONFIG_HAVE_FUNCTION_GRAPH_TRACER=yCONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=yCONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=yCONFIG_HAVE_DYNAMIC_FTRACE=yCONFIG_HAVE_FTRACE_MCOUNT_RECORD=yCONFIG_HAVE_SYSCALL_TRACEPOINTS=yCONFIG_RING_BUFFER=yCONFIG_EVENT_TRACING=yCONFIG_CONTEXT_SWITCH_TRACER=yCONFIG_RING_BUFFER_ALLOW_SWAP=yCONFIG_TRACING=yCONFIG_GENERIC_TRACER=yCONFIG_TRACING_SUPPORT=yCONFIG_FTRACE=y
# CONFIG_FUNCTION_TRACER is not set
# CONFIG_IRQSOFF_TRACER is not set
# CONFIG_SCHED_TRACER is not set
# CONFIG_FTRACE_SYSCALLS is not setCONFIG_BRANCH_PROFILE_NONE=y
# CONFIG_PROFILE_ANNOTATED_BRANCHES is not set
# CONFIG_PROFILE_ALL_BRANCHES is not set
# CONFIG_STACK_TRACER is not setCONFIG_BLK_DEV_IO_TRACE=y
# CONFIG_FTRACE_STARTUP_TEST is not set
# CONFIG_MMIOTRACE is not set
# CONFIG_RING_BUFFER_BENCHMARK is not set
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
# CONFIG_DYNAMIC_DEBUG is not set
# CONFIG_DMA_API_DEBUG is not set
# CONFIG_ATOMIC64_SELFTEST is not set
# CONFIG_SAMPLES is not setCONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not setCONFIG_HAVE_ARCH_KMEMCHECK=yCONFIG_STRICT_DEVMEM=y
# CONFIG_X86_VERBOSE_BOOTUP is not setCONFIG_EARLY_PRINTK=y
# CONFIG_EARLY_PRINTK_DBGP is not set
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_X86_PTDUMP is not setCONFIG_DEBUG_RODATA=y
# CONFIG_DEBUG_RODATA_TEST is not set
# CONFIG_IOMMU_DEBUG is not set
# CONFIG_IOMMU_STRESS is not setCONFIG_HAVE_MMIOTRACE_SUPPORT=yCONFIG_IO_DELAY_TYPE_0X80=0CONFIG_IO_DELAY_TYPE_0XED=1CONFIG_IO_DELAY_TYPE_UDELAY=2CONFIG_IO_DELAY_TYPE_NONE=3CONFIG_IO_DELAY_0X80=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not setCONFIG_DEFAULT_IO_DELAY_TYPE=0
# CONFIG_DEBUG_BOOT_PARAMS is not set
# CONFIG_CPA_DEBUG is not set
# CONFIG_OPTIMIZE_INLINING is not set
# CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is not set
#
# Security options
#CONFIG_KEYS=yCONFIG_KEYS_DEBUG_PROC_KEYS=yCONFIG_SECURITY=y
# CONFIG_SECURITYFS is not setCONFIG_SECURITY_NETWORK=y
# CONFIG_SECURITY_NETWORK_XFRM is not set
# CONFIG_SECURITY_PATH is not set
# CONFIG_SECURITY_TOMOYO is not set
# CONFIG_SECURITY_APPARMOR is not set
# CONFIG_IMA is not setCONFIG_DEFAULT_SECURITY_DAC=yCONFIG_DEFAULT_SECURITY=""CONFIG_CRYPTO=y
#
# Crypto core or helper
#CONFIG_CRYPTO_ALGAPI=yCONFIG_CRYPTO_ALGAPI2=yCONFIG_CRYPTO_AEAD2=yCONFIG_CRYPTO_BLKCIPHER=yCONFIG_CRYPTO_BLKCIPHER2=yCONFIG_CRYPTO_HASH=yCONFIG_CRYPTO_HASH2=yCONFIG_CRYPTO_RNG2=yCONFIG_CRYPTO_PCOMP2=yCONFIG_CRYPTO_MANAGER=yCONFIG_CRYPTO_MANAGER2=yCONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
# CONFIG_CRYPTO_GF128MUL is not set
# CONFIG_CRYPTO_NULL is not setCONFIG_CRYPTO_WORKQUEUE=y
# CONFIG_CRYPTO_CRYPTD is not set
# CONFIG_CRYPTO_AUTHENC is not set
#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_SEQIV is not set
#
# Block modes
#CONFIG_CRYPTO_CBC=y
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_CTS is not setCONFIG_CRYPTO_ECB=y
# CONFIG_CRYPTO_LRW is not setCONFIG_CRYPTO_PCBC=y
# CONFIG_CRYPTO_XTS is not set
#
# Hash modes
#CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_VMAC is not set
#
# Digest
#CONFIG_CRYPTO_CRC32C=yCONFIG_CRYPTO_CRC32C_INTEL=y
# CONFIG_CRYPTO_GHASH is not set
# CONFIG_CRYPTO_MD4 is not setCONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_RMD128 is not set
# CONFIG_CRYPTO_RMD160 is not set
# CONFIG_CRYPTO_RMD256 is not set
# CONFIG_CRYPTO_RMD320 is not setCONFIG_CRYPTO_SHA1=y
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL is not set
#
# Ciphers
#
# CONFIG_CRYPTO_AES is not set
# CONFIG_CRYPTO_AES_X86_64 is not set
# CONFIG_CRYPTO_AES_NI_INTEL is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SALSA20_X86_64 is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_X86_64 is not set
#
# Compression
#
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_ZLIB is not set
# CONFIG_CRYPTO_LZO is not set
#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not setCONFIG_CRYPTO_HW=y
# CONFIG_CRYPTO_DEV_PADLOCK is not set
# CONFIG_CRYPTO_DEV_HIFN_795X is not setCONFIG_HAVE_KVM=y
# CONFIG_VIRTUALIZATION is not setCONFIG_BINARY_PRINTF=y
#
# Library routines
#CONFIG_BITREVERSE=yCONFIG_GENERIC_FIND_FIRST_BIT=yCONFIG_GENERIC_FIND_NEXT_BIT=yCONFIG_GENERIC_FIND_LAST_BIT=y
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC16 is not setCONFIG_CRC_T10DIF=y
# CONFIG_CRC_ITU_T is not setCONFIG_CRC32=y
# CONFIG_CRC7 is not setCONFIG_LIBCRC32C=yCONFIG_ZLIB_INFLATE=yCONFIG_ZLIB_DEFLATE=yCONFIG_LZO_DECOMPRESS=yCONFIG_DECOMPRESS_GZIP=yCONFIG_DECOMPRESS_BZIP2=yCONFIG_DECOMPRESS_LZMA=yCONFIG_DECOMPRESS_LZO=yCONFIG_HAS_IOMEM=yCONFIG_HAS_IOPORT=yCONFIG_HAS_DMA=yCONFIG_NLATTR=y
Quoted 27 lines · Ingo Molnar
Quoted 10 lines · Mathieu Desnoyers
(on a uniprocessor 2.0 GHz Pentium M)
* Without the patch:
- wakeup-latency with
SIGEV_THREADin parallel with youtube video and make -j10maximum latency: 50107.8 µs
average latency: 6609.2 µs
missed timer events: 0I tried your patches on a similar UP system, using
wakeup-latency.c. I also measured the vanilla upstream kernel (cced86a) with the default granularity settings, and also vanilla with a sched_min_granularity/3 tune (patch attached below for that).I got the following results (make -j10 kbuild load, average of 3 runs):
vanilla:
maximum latency: 38278.9 µs
average latency: 7730.1 µsmathieu-dyn:
Quoted 7 lines
maximum latency: 28698.8 µs
average latency: 7757.1 µspeterz-min_gran/3:
maximum latency: 22702.1 µs
average latency: 6684.8 µs
One thing that springs to mind with make is that it does vfork, so kinda sorta continues running in drag, so shouldn't get credit for sleeping, as that introduces bogus spread. Post vfork parent notification time adjustment may suffice, think I'll try that.
-Mike
Quoted 33 lines · * Mike Galbraith ([email protected]) wrote:
Quoted 32 lines · Ingo Molnar
Quoted 10 lines · Mathieu Desnoyers
(on a uniprocessor 2.0 GHz Pentium M)
* Without the patch:
- wakeup-latency with
SIGEV_THREADin parallel with youtube video and make -j10maximum latency: 50107.8 µs
average latency: 6609.2 µs
missed timer events: 0I tried your patches on a similar UP system, using
wakeup-latency.c. I also measured the vanilla upstream kernel (cced86a) with the default granularity settings, and also vanilla with a sched_min_granularity/3 tune (patch attached below for that).I got the following results (make -j10 kbuild load, average of 3 runs):
vanilla:
maximum latency: 38278.9 µs
average latency: 7730.1 µsmathieu-dyn:
maximum latency: 28698.8 µs
average latency: 7757.1 µspeterz-min_gran/3:
Quoted 7 lines
Quoted 2 lines
maximum latency: 22702.1 µs
average latency: 6684.8 µsOne thing that springs to mind with make is that it does vfork, so kinda sorta continues running in drag, so shouldn't get credit for sleeping, as that introduces bogus spread. Post vfork parent notification time adjustment may suffice, think I'll try that.
Hrm, I might be misunderstanding what you are saying here, but when a new process/thread is forked and woken up, we fall in the "initial" case of place_entity, so we increase the vruntime of a whole slice rather than getting credit for sleeping.
Or am I missing your point ?
Thanks,
Mathieu
Signature · 4 lines
Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
Quoted 42 lines · Mathieu Desnoyers
Quoted 33 lines · * Mike Galbraith ([email protected]) wrote:
Quoted 32 lines · Ingo Molnar
Quoted 10 lines · Mathieu Desnoyers
(on a uniprocessor 2.0 GHz Pentium M)
* Without the patch:
- wakeup-latency with
SIGEV_THREADin parallel with youtube video and make -j10maximum latency: 50107.8 µs
average latency: 6609.2 µs
missed timer events: 0I tried your patches on a similar UP system, using
wakeup-latency.c. I also measured the vanilla upstream kernel (cced86a) with the default granularity settings, and also vanilla with a sched_min_granularity/3 tune (patch attached below for that).I got the following results (make -j10 kbuild load, average of 3 runs):
vanilla:
maximum latency: 38278.9 µs
average latency: 7730.1 µsmathieu-dyn:
maximum latency: 28698.8 µs
average latency: 7757.1 µspeterz-min_gran/3:
Quoted 7 lines
Quoted 2 lines
maximum latency: 22702.1 µs
average latency: 6684.8 µsOne thing that springs to mind with make is that it does vfork, so kinda sorta continues running in drag, so shouldn't get credit for sleeping, as that introduces bogus spread. Post vfork parent notification time adjustment may suffice, think I'll try that.
Quoted 6 lines
Hrm, I might be misunderstanding what you are saying here, but when a new process/thread is forked and woken up, we fall in the "initial" case of
place_entity, so we increase the vruntime of a whole slice rather than getting credit for sleeping.Or am I missing your point ?
Yes and no. I'm pondering the parent, but by the same token, the vfork child shouldn't be penalized either.
Does your latency go down drastically if you turn START_DEBIT off? Seems like it should. Perhaps START_DEBIT should not start a task further right than rightmost. I've done that before.
maximum latency: 19221.5 µs
average latency: 5159.0 µs
missed timer events: 0
maximum latency: 43901.0 µs
average latency: 8430.1 µs
missed timer events: 0
Turning it off here cut latency roughly in half (i've piddled vfork though, but not completely). Limiting child placement to no further right than rightmost should help quite a bit.
-Mike
Quoted 15 lines · Mike Galbraith
Quoted 1 line · Mathieu Desnoyers
Or am I missing your point ?
Yes and no. I'm pondering the parent, but by the same token, the vfork child shouldn't be penalized either.
Does your latency go down drastically if you turn
START_DEBIToff? Seems like it should. PerhapsSTART_DEBITshould not start a task further right than rightmost. I've done that before.maximum latency: 19221.5 µs
average latency: 5159.0 µs
missed timer events: 0
Quoted 7 lines
maximum latency: 43901.0 µs
average latency: 8430.1 µs
missed timer events: 0Turning it off here cut latency roughly in half (i've piddled vfork though, but not completely). Limiting child placement to no further right than rightmost should help quite a bit.
Very interesting observation. Mathieu, mind testing Mike's suggestion with wakeup-latency.c?
Thanks,
Ingo
Quoted 21 lines · Ingo Molnar
Quoted 19 lines · Mike Galbraith
Quoted 1 line · Mathieu Desnoyers
Or am I missing your point ?
Yes and no. I'm pondering the parent, but by the same token, the vfork child shouldn't be penalized either.
Does your latency go down drastically if you turn
START_DEBIToff? Seems like it should. PerhapsSTART_DEBITshould not start a task further right than rightmost. I've done that before.maximum latency: 19221.5 µs
average latency: 5159.0 µs
missed timer events: 0maximum latency: 43901.0 µs
average latency: 8430.1 µs
missed timer events: 0
Quoted 6 lines
Quoted 3 lines
Turning it off here cut latency roughly in half (i've piddled vfork though, but not completely). Limiting child placement to no further right than rightmost should help quite a bit.
Very interesting observation. Mathieu, mind testing Mike's suggestion with
wakeup-latency.c?
I'm sure it will. I think the problem is that light thread forks, the child takes vruntime hit, so the parent's lag isn't _useful_. It may preempt, but the work it's trying to get done is delayed massively unfairly.
btw, setting parent's lag to that of the child on parent wakeup for the vfork case seems to work fine, kbuild no longer gets the advantage it would vs static load if START_DEBIT were disabled. That leaves what to do with plain old fork/clone though. Leaving START_DEBIT in place for fork/clone vs a fair vfork load blows chunks, as does running a forky load vs some static load without START_DEBIT.
Sticky wicket. We need a better fork fairness gizmo.
-Mike
Quoted 1 line · Mike Galbraith
Sticky wicket. We need a better fork fairness gizmo.
Like maybe re-inventing O(1)'s fork penalty + return on exit instead of START_DEBIT penalizing the child? Child of lagging parent needs to run NOW, just as any other lagging task wakeup, but fork/clone dare not be an advantage.
-Mike
Peter Zijlstra
maintainerQuoted 1 line · Mike Galbraith
We need a better fork fairness gizmo.
Proper zero-lag insertion would do. Much sadness in that tracking that costs a u64 mult per enqueu/dequeue and using it adds a s64 div.
But if you want, have a play with:
--- kernel/sched.c | 3 + kernel/sched_debug.c | 31 +++++------ kernel/sched_fair.c | 136 +++++++++++++++++++++++++++++++++++----------- kernel/sched_features.h | 6 -- 4 files changed, 120 insertions(+), 56 deletions(-)
kernel/sched.c +3 -0
@@ -314,6 +314,9 @@ struct cfs_rq {struct load_weight load;unsigned long nr_running; +s64 avg_vruntime; +u64 avg_load; +u64 exec_clock;u64 min_vruntime;
kernel/sched_debug.c +14 -17
@@ -162,10 +162,9 @@ static void task_group_path(struct task_group *tg, char *buf, int buflen)void print_cfs_rq (struct seq_file *m,int cpu,struct cfs_rq *cfs_rq) { -s64 MIN_vruntime =-1 , min_vruntime, max_vruntime =-1 , - spread, rq0_min_vruntime, spread0; +s64 left_vruntime =-1 , min_vruntime, right_vruntime =-1 , spread;struct rq *rq =cpu_rq (cpu); -struct sched_entity *last; +struct sched_entity *last, *first;unsigned long flags;#if defined(CONFIG_CGROUP_SCHED ) && defined(CONFIG_FAIR_GROUP_SCHED )
@@ -182,26 +181,24 @@ void print_cfs_rq(struct seq_file *m, int cpu, struct cfs_rq *cfs_rq) SPLIT_NS(cfs_rq->exec_clock));raw_spin_lock_irqsave (&rq->lock, flags); -if (cfs_rq->rb_leftmost) - MIN_vruntime = (__pick_next_entity (cfs_rq))->vruntime; + first =__pick_first_entity (cfs_rq); +if (first) + left_vruntime = first->vruntime; last =__pick_last_entity (cfs_rq);if (last) - max_vruntime = last->vruntime; + right_vruntime = last->vruntime; min_vruntime = cfs_rq->min_vruntime; - rq0_min_vruntime =cpu_rq (0 )->cfs.min_vruntime;raw_spin_unlock_irqrestore (&rq->lock, flags); -SEQ_printf (m," .%-30s: %Ld.%06ld\n" ,"MIN_vruntime" , -SPLIT_NS (MIN_vruntime)); +SEQ_printf (m," .%-30s: %Ld.%06ld\n" ,"left_vruntime" , +SPLIT_NS (left_vruntime));SEQ_printf (m," .%-30s: %Ld.%06ld\n" ,"min_vruntime" ,SPLIT_NS (min_vruntime)); -SEQ_printf (m," .%-30s: %Ld.%06ld\n" ,"max_vruntime" , -SPLIT_NS (max_vruntime)); - spread = max_vruntime - MIN_vruntime; -SEQ_printf (m," .%-30s: %Ld.%06ld\n" ,"spread" , -SPLIT_NS (spread)); - spread0 = min_vruntime - rq0_min_vruntime; -SEQ_printf (m," .%-30s: %Ld.%06ld\n" ,"spread0" , -SPLIT_NS (spread0)); +SEQ_printf (m," .%-30s: %Ld.%06ld\n" ,"avg_vruntime" , +SPLIT_NS (avg_vruntime (cfs_rq))); +SEQ_printf (m," .%-30s: %Ld.%06ld\n" ,"right_vruntime" , +SPLIT_NS (right_vruntime)); + spread = right_vruntime - left_vruntime; +SEQ_printf (m," .%-30s: %Ld.%06ld\n" ,"spread" ,SPLIT_NS (spread));SEQ_printf (m," .%-30s: %ld\n" ,"nr_running" , cfs_rq->nr_running);SEQ_printf (m," .%-30s: %ld\n" ,"load" , cfs_rq->load.weight);
kernel/sched_fair.c +103 -33
187 lines not on this page · raw message
kernel/sched_features.h +0 -6
@@ -6,12 +6,6 @@SCHED_FEAT (GENTLE_FAIR_SLEEPERS ,1 )/* -* Place new tasks ahead so that they do not starve already running -* tasks - */ -SCHED_FEAT (START_DEBIT ,1 ) - -/* * Should wakeups try to preempt running tasks. */SCHED_FEAT (WAKEUP_PREEMPT ,1 )
Quoted 5 lines · Peter Zijlstra
Quoted 1 line · Mike Galbraith
We need a better fork fairness gizmo.
Proper zero-lag insertion would do. Much sadness in that tracking that costs a u64 mult per enqueu/dequeue and using it adds a s64 div.
(math _sucks_:)
Quoted 1 line
But if you want, have a play with:
maximum latency: 48475.3 µs
average latency: 6881.4 µs
missed timer events: 0
Darn.
make -j3 is gaining a tad over a hog as well, roughly the same as turning START_DEBIT off.
-Mike
Peter Zijlstra
maintainerQuoted 11 lines · Mike Galbraith
Quoted 5 lines · Peter Zijlstra
Quoted 1 line · Mike Galbraith
We need a better fork fairness gizmo.
Proper zero-lag insertion would do. Much sadness in that tracking that costs a u64 mult per enqueu/dequeue and using it adds a s64 div.
(math _sucks_:)
Quoted 1 line
But if you want, have a play with:
Quoted 8 lines
maximum latency: 48475.3 µs
average latency: 6881.4 µs
missed timer events: 0Darn.
make -j3 is gaining a tad over a hog as well, roughly the same as turning
START_DEBIToff.
Hrmm,. could it be fair_sleeper muck placing too many tasks too far left on wakeup starving others?
Quoted 16 lines · Peter Zijlstra
Quoted 15 lines · Mike Galbraith
Quoted 5 lines · Peter Zijlstra
Quoted 1 line · Mike Galbraith
We need a better fork fairness gizmo.
Proper zero-lag insertion would do. Much sadness in that tracking that costs a u64 mult per enqueu/dequeue and using it adds a s64 div.
(math _sucks_:)
Quoted 1 line
But if you want, have a play with:
maximum latency: 48475.3 µs
average latency: 6881.4 µs
missed timer events: 0
Quoted 8 lines
Quoted 4 lines
Darn.
make -j3 is gaining a tad over a hog as well, roughly the same as turning
START_DEBIToff.Hrmm,. could it be
fair_sleepermuck placing too many tasks too far left on wakeup starving others?
Yeah, pretty much has to be fair_sleepers holding others off for too long. (A shiny new preemption model is about the only thing that can make that go away) Perhaps lag should be negated if you've received a reasonable chunk or something.. but what we really want is a service deadline.
-Mike
Peter Zijlstra
maintainerQuoted 3 lines · Mike Galbraith
Perhaps lag should be negated if you've received a reasonable chunk or something.. but what we really want is a service deadline.
Hey, I've got a patch for that too :-)
Not rebased to anything current, but should be able to get frobbed onto the last zero-lag thingy without too much grief (I think).
---
Subject:
From: Peter Zijlstra <[email protected]>
Date: Tue Apr 20 16:50:03 CEST 2010
LKML-Reference: <new-submission>
--- include/linux/sched.h | 17 +- kernel/sched.c | 8 kernel/sched_debug.c | 28 +-- kernel/sched_fair.c | 388 ++++++++++++++++++++++++++++++++++++------------ kernel/sched_features.h | 5 kernel/sysctl.c | 4 6 files changed, 337 insertions(+), 113 deletions(-)
kernel/sched_debug.c +16 -12
@@ -94,20 +94,22 @@ print_task(struct seq_file *m, struct rqelse SEQ_printf (m," " ); -SEQ_printf (m,"%15s %5d %9Ld.%06ld %9Ld %5d " , +SEQ_printf (m,"%15s %5d %9Ld.%06ld %c %9Ld.%06ld %9Ld.%06ld %9Ld.%06ld %9Ld %5d " , p->comm, p->pid,SPLIT_NS (p->se.vruntime), +entity_eligible (cfs_rq_of (&p->se), &p->se) ?'E' :'N' , +SPLIT_NS (p->se.deadline), +SPLIT_NS (p->se.slice), +SPLIT_NS (p->se.sum_exec_runtime), (long long )(p->nvcsw + p->nivcsw), p->prio); +SEQ_printf (m,"%9Ld.%06ld" , #ifdef CONFIG_SCHEDSTATS -SEQ_printf (m,"%9Ld.%06ld %9Ld.%06ld %9Ld.%06ld" , -SPLIT_NS (p->se.vruntime), -SPLIT_NS (p->se.sum_exec_runtime), -SPLIT_NS (p->se.statistics.sum_sleep_runtime)); + SPLIT_NS(p->se.statistics.sum_sleep_runtime) #else -SEQ_printf (m,"%15Ld %15Ld %15Ld.%06ld %15Ld.%06ld %15Ld.%06ld" , -0LL ,0LL ,0LL ,0L ,0LL ,0L ,0LL ,0L ); +0LL ,0L #endif + );#ifdef CONFIG_CGROUP_SCHED {
@@ -129,10 +131,12 @@ static void print_rq(struct seq_file *m,SEQ_printf (m,"\nrunnable tasks:\n" -" task PID tree-key switches prio" -" exec-runtime sum-exec sum-sleep\n" -"------------------------------------------------------" -"----------------------------------------------------\n" ); +" task PID vruntime e deadline" +" slice exec_runtime switches prio" +" sum-sleep\n" +"----------------------------------------------------------" +"---------------------------------" +"-----------------\n" );read_lock_irqsave (&tasklist_lock, flags);
@@ -326,7 +330,7 @@ static int sched_debug_show(struct seq_f SEQ_printf(m, " .%-40s: %Ld.%06ld\n", #x, SPLIT_NS(x))P (jiffies);PN (sysctl_sched_latency); -PN (sysctl_sched_min_granularity); +PN (sysctl_sched_slice);PN (sysctl_sched_wakeup_granularity);PN (sysctl_sched_child_runs_first);P (sysctl_sched_features);
kernel/sched_fair.c +297 -91
556 lines not on this page · raw message
include/linux/sched.h +12 -5
@@ -1028,9 +1028,11 @@ struct sched_domain;#define WF_FORK 0x02/* child wakeup after fork */ #define WF_INTERACTIVE 0x04 -#define ENQUEUE_WAKEUP 0x1 -#define ENQUEUE_WAKING 0x2 -#define ENQUEUE_HEAD 0x4 +#define ENQUEUE_WAKEUP 0x01 +#define ENQUEUE_WAKING 0x02 +#define ENQUEUE_HEAD 0x04 +#define ENQUEUE_IO 0x08 +#define ENQUEUE_LATENCY 0x10#define DEQUEUE_SLEEP 0x1
@@ -1125,13 +1127,18 @@ struct sched_entity {struct rb_node run_node;struct list_head group_node; unsigned int on_rq : 1, - interactive : 1; + interactive : 8;u64 exec_start;u64 sum_exec_runtime;u64 vruntime;u64 prev_sum_exec_runtime; +u64 deadline; +u64 min_deadline; +u64 lag; +u64 slice; +u64 nr_migrations;#ifdef CONFIG_SCHEDSTATS
@@ -1871,7 +1878,7 @@ static inline void wake_up_idle_cpu(int#endif extern unsigned int sysctl_sched_latency; -extern unsigned int sysctl_sched_min_granularity; +extern unsigned int sysctl_sched_slice;extern unsigned int sysctl_sched_wakeup_granularity;extern unsigned int sysctl_sched_shares_ratelimit;extern unsigned int sysctl_sched_shares_thresh;
kernel/sysctl.c +2 -2
@@ -282,8 +282,8 @@ static struct ctl_table kern_table[] = { },#ifdef CONFIG_SCHED_DEBUG { - .procname = "sched_min_granularity_ns", - .data = &sysctl_sched_min_granularity, + .procname = "sched_slice_ns", + .data = &sysctl_sched_slice, .maxlen = sizeof(unsigned int), .mode = 0644, .proc_handler = sched_proc_update_handler,
kernel/sched.c +5 -3
@@ -2365,7 +2365,7 @@ static int try_to_wake_up(struct task_stif (current->sched_wake_interactive || wake_flags &WF_INTERACTIVE || current->se.interactive) - p->se.interactive =1 ; + en_flags |=ENQUEUE_LATENCY ; } this_cpu =get_cpu ();
@@ -2442,6 +2442,8 @@ out_activate: cpu == this_cpu, en_flags); success =1 ; out_running: +trace_printk ("sched_wakeup: wake_flags: %d enqueue_flags: %d\n" , + wake_flags, en_flags);ttwu_post_activation (p, rq, wake_flags, success); out:task_rq_unlock (rq, &flags);
@@ -2515,6 +2517,7 @@ static void __sched_fork(struct task_str p->se.sum_exec_runtime =0 ; p->se.prev_sum_exec_runtime =0 ; p->se.nr_migrations =0 ; + p->se.lag =0 ;#ifdef CONFIG_SCHEDSTATS memset (&p->se.statistics,0 ,sizeof (p->se.statistics));
@@ -5410,8 +5413,7 @@ static void update_sysctl(void)#define SET_SYSCTL (name) \ (sysctl_##name = (factor) * normalized_sysctl_##name) -SET_SYSCTL (sched_min_granularity); -SET_SYSCTL (sched_latency); +SET_SYSCTL (sched_slice);SET_SYSCTL (sched_wakeup_granularity);SET_SYSCTL (sched_shares_ratelimit);#undef SET_SYSCTL
kernel/sched_features.h +5 -0
@@ -52,3 +52,8 @@ SCHED_FEAT(INTERACTIVE, 0)* release the lock. Decreases scheduling overhead. */ SCHED_FEAT(OWNER_SPIN, 1) + +SCHED_FEAT(EEVDF, 1) +SCHED_FEAT(FAIR_DEADLINE, 1) +SCHED_FEAT(ZERO_LAG, 0) +SCHED_FEAT (PRESERVE_LAG ,0 )
Quoted 9 lines · Peter Zijlstra
Quoted 3 lines · Mike Galbraith
Perhaps lag should be negated if you've received a reasonable chunk or something.. but what we really want is a service deadline.
Hey, I've got a patch for that too :-)
Not rebased to anything current, but should be able to get frobbed onto the last zero-lag thingy without too much grief (I think).
A frobbing I shall go.
Quoted 6 lines
+/*
+ * Entity is eligible once it received less service than it ought to have,
+ * eg. lag >= 0.
+ *
+ *lag_i=S_i-s_i= w_i*(V -w_i)
+ *
Quoted 8 lines
+ *
lag_i>=0 -> V >=v_i
+ *
+ * \Sum (v_i- v)*w_i
+ * V = ------------------ + v
+ * \Sumw_i
+ *
+ *lag_i>= 0 -> \Sum (v_i- v)*w_i >= (v_i- v)*(\Sumw_i)
+ */
Ew, more of that icky stuff.
-Mike
Peter Zijlstra
maintainerQuoted 11 lines · Peter Zijlstra
+/*
+ * Earliest Eligible Virtual Deadline First
+ *
+ * In order to provide latency guarantees for different request sizes
+ * EEVDF selects the best runnable task from two criteria:
+ *
+ * 1) the task must be eligible (must be owed service)
+ *
+ * 2) from those tasks that meet 1), we select the one
+ * with the earliest virtual deadline.
+ *
Quoted 8 lines
+ * We can do this in O(log n) time due to an augmented RB-tree. The
+ * tree keeps the entries sorted on service, but also functions as a
+ * heap based on the deadline by keeping:
+ *
+ *se->min_deadline=min(se->deadline, se->{left,right}->min_deadline)
+ *
+ * Which allows an EDF like search on (sub)trees.
+ */
I just realized, this doesn't do what we wanted.. the virtual deadline stuff is handy when you've got tasks with different QoS, but we don't have that, they're all the same due to our task model.
What we want is real deadlines, the patch provides the infrastructure, let me frob something for that.
Peter Zijlstra
maintainerQuoted 2 lines · Peter Zijlstra
What we want is real deadlines, the patch provides the infrastructure, let me frob something for that.
Here, real deadline, but totally untested (except for compile).
Please read through the logic. The idea was to do as we always do, except keep a deadline on enqueue for now + __sched_period, once we find that a deadline expired, we force run that task.
I frobbed the wakeup-preemption to never preempt a deadline expired task, but that might be a little harsh.
Its all a lot of extra code, but have a tinker to see if you can make it do what seems wanted ;-)
--- include/linux/sched.h | 5 +- kernel/sched.c | 4 + kernel/sched_debug.c | 57 ++++---- kernel/sched_fair.c | 360 +++++++++++++++++++++++++++++++++++++---------- kernel/sched_features.h | 7 +- 5 files changed, 327 insertions(+), 106 deletions(-)
include/linux/sched.h +4 -1
@@ -1097,7 +1097,6 @@ struct sched_statistics {u64 block_start;u64 block_max;u64 exec_max; -u64 slice_max;u64 nr_migrations_cold;u64 nr_failed_migrations_affine;
@@ -1128,6 +1127,10 @@ struct sched_entity {u64 vruntime;u64 prev_sum_exec_runtime; +u64 deadline; +u64 min_deadline; +u64 lag; +u64 nr_migrations;#ifdef CONFIG_SCHEDSTATS
kernel/sched.c +4 -0
@@ -314,6 +314,9 @@ struct cfs_rq {struct load_weight load;unsigned long nr_running; +s64 avg_vruntime; +u64 avg_load; +u64 exec_clock;u64 min_vruntime;
@@ -2497,6 +2500,7 @@ static void __sched_fork(struct task_struct *p) p->se.sum_exec_runtime =0 ; p->se.prev_sum_exec_runtime =0 ; p->se.nr_migrations =0 ; + p->se.lag =0 ;#ifdef CONFIG_SCHEDSTATS memset (&p->se.statistics,0 ,sizeof (p->se.statistics));
kernel/sched_debug.c +27 -30
107 lines not on this page · raw message
kernel/sched_fair.c +286 -74
534 lines not on this page · raw message
kernel/sched_features.h +6 -1
@@ -3,13 +3,14 @@* them to run sooner, but does not allow tons of sleepers to * rip the spread apart. */ +SCHED_FEAT(FAIR_SLEEPERS, 1)SCHED_FEAT (GENTLE_FAIR_SLEEPERS ,1 )/* * Place new tasks ahead so that they do not starve already running * tasks */ -SCHED_FEAT (START_DEBIT ,1 ) +SCHED_FEAT (START_DEBIT ,0 )/* * Should wakeups try to preempt running tasks.
@@ -61,3 +62,7 @@ SCHED_FEAT(ASYM_EFF_LOAD, 1)* release the lock. Decreases scheduling overhead. */ SCHED_FEAT(OWNER_SPIN, 1) + +SCHED_FEAT(DEADLINE, 1) +SCHED_FEAT(PRESERVE_LAG, 0) +SCHED_FEAT (ZERO_LAG ,0 )
Peter Zijlstra
maintainerkernel/sched_fair.c static struct sched_entity *__pick_last_entity(struct cfs_rq *cfs_rq) · line 553
Quoted 5 lines · Peter Zijlstra
kernel/sched_fair.c +5
-0+ +if (node->rb_left && +se_of (node->rb_left)->min_deadline == se->min_deadline) { + node = node->rb_left; + }
There wants to be a continue in that branch.
Quoted 5 lines · Peter Zijlstra
Quoted 2 lines · Peter Zijlstra
What we want is real deadlines, the patch provides the infrastructure, let me frob something for that.
Here, real deadline, but totally untested (except for compile).
You're fast. Now to see if I can find the early forever Loop :)
Quoted 3 lines
Please read through the logic. The idea was to do as we always do, except keep a deadline on enqueue for now +
__sched_period, once we find that a deadline expired, we force run that task.
Yeah, I'll go read/piddle.
-Mike
Quoted 22 lines · * Ingo Molnar ([email protected]) wrote:
Quoted 19 lines · Mike Galbraith
Quoted 1 line · Mathieu Desnoyers
Or am I missing your point ?
Yes and no. I'm pondering the parent, but by the same token, the vfork child shouldn't be penalized either.
Does your latency go down drastically if you turn
START_DEBIToff? Seems like it should. PerhapsSTART_DEBITshould not start a task further right than rightmost. I've done that before.maximum latency: 19221.5 µs
average latency: 5159.0 µs
missed timer events: 0maximum latency: 43901.0 µs
average latency: 8430.1 µs
missed timer events: 0
Quoted 6 lines
Quoted 3 lines
Turning it off here cut latency roughly in half (i've piddled vfork though, but not completely). Limiting child placement to no further right than rightmost should help quite a bit.
Very interesting observation. Mathieu, mind testing Mike's suggestion with
wakeup-latency.c?
Sure. this is with the smaller min_granularity:
With START_DEBIT:
maximum latency: 21111.1 µs
average latency: 4188.2 µs
missed timer events: 0
Without:
maximum latency: 6670.2 µs
average latency: 1586.0 µs
missed timer events: 0
So yes, as expected, it makes a huge difference. This is because SIGEV_THREAD creates a new thread each time the timer fires, and newly created tasks are put at the end of the runqueue with START_DEBIT.
However, removing START_DEBIT makes my Xorg feel less responsive (again, just my own impression). We might need a more suitable way to deal with forks than just putting the newly forked task at the end of the spread, but just putting it at the beginning of the spread does not seem to do well neither.
One idea: we could temporarily tweak the nice value of both the parent and the child after a fork to a lower nice value, but only apply this for their first slice after the fork. The goal behind this is that their respective vruntime will increment faster in the first slice after the fork, so a fork bomb (worse-case) will end up running with a very very low nice level. With this measure in place, START_DEBIT might not be needed. Thoughts ?
Thanks,
Mathieu
Quoted 4 lines
Thanks,
Ingo
Signature · 4 lines
Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
Quoted 53 lines · * Mathieu Desnoyers ([email protected]) wrote:
Quoted 22 lines · * Ingo Molnar ([email protected]) wrote:
Quoted 19 lines · Mike Galbraith
Quoted 1 line · Mathieu Desnoyers
Or am I missing your point ?
Yes and no. I'm pondering the parent, but by the same token, the vfork child shouldn't be penalized either.
Does your latency go down drastically if you turn
START_DEBIToff? Seems like it should. PerhapsSTART_DEBITshould not start a task further right than rightmost. I've done that before.maximum latency: 19221.5 µs
average latency: 5159.0 µs
missed timer events: 0maximum latency: 43901.0 µs
average latency: 8430.1 µs
missed timer events: 0Quoted 6 lines
Quoted 3 lines
Turning it off here cut latency roughly in half (i've piddled vfork though, but not completely). Limiting child placement to no further right than rightmost should help quite a bit.
Very interesting observation. Mathieu, mind testing Mike's suggestion with
wakeup-latency.c?Sure. this is with the smaller
min_granularity:With
START_DEBIT:maximum latency: 21111.1 µs
average latency: 4188.2 µs
missed timer events: 0Without:
maximum latency: 6670.2 µs
average latency: 1586.0 µs
missed timer events: 0So yes, as expected, it makes a huge difference. This is because
SIGEV_THREADcreates a new thread each time the timer fires, and newly created tasks are put at the end of the runqueue withSTART_DEBIT.However, removing
START_DEBITmakes my Xorg feel less responsive (again, just my own impression). We might need a more suitable way to deal with forks than just putting the newly forked task at the end of the spread, but just putting it at the beginning of the spread does not seem to do well neither.
Quoted 6 lines
One idea: we could temporarily tweak the nice value of both the parent and the child after a fork to a lower nice value, but only apply this for their first slice after the fork. The goal behind this is that their respective vruntime will increment faster in the first slice after the fork, so a fork bomb (worse-case) will end up running with a very very low nice level. With this measure in place,
START_DEBITmight not be needed. Thoughts ?
A small note: Steven made me realize that when I say "low nice level" here, I actually mean "high nice values". Less is more when we talk about nice levels.
Thanks,
Mathieu
Quoted 15 lines
Thanks,
Mathieu
Quoted 4 lines
Thanks,
Ingo
Signature · 4 lines
Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
Signature · 4 lines
Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
Quoted 5 lines · * Ingo Molnar ([email protected]) wrote:
Quoted 2 lines · Mathieu Desnoyers
(on a uniprocessor 2.0 GHz Pentium M)
Quoted 9 lines
Quoted 8 lines
* Without the patch:
- wakeup-latency with
SIGEV_THREADin parallel with youtube video and make -j10maximum latency: 50107.8 µs
average latency: 6609.2 µs
missed timer events: 0
Hi Ingo,
Thanks for looking into this,
Quoted 34 lines
I tried your patches on a similar UP system, using
wakeup-latency.c. I also measured the vanilla upstream kernel (cced86a) with the default granularity settings, and also vanilla with a sched_min_granularity/3 tune (patch attached below for that).I got the following results (make -j10 kbuild load, average of 3 runs):
vanilla:
maximum latency: 38278.9 µs
average latency: 7730.1 µsmathieu-dyn:
maximum latency: 28698.8 µs
average latency: 7757.1 µspeterz-min_gran/3:
maximum latency: 22702.1 µs
average latency: 6684.8 µsA couple of notes:
- As can be seen from the raw results further below, the max-latency
sched-latency.cnumbers were very noisy with all 3 kernels. (This is typical of most maxium latency metrics). But it can be said that within statistical noise both your patches and peterz's patch reduced maximum latencies - as expected.- average latency seems to have gone down a bit more via the min_gran/3 patch. Your patch produced a faster-than-vanilla result in one of the runs - but the numbers are too noisy in general.
Quoted 5 lines
- ( Measurement methodology: find below the raw results of the 3 runs pasted, and find attached the kernel config i used. (I applied your second patch with a trivial conflict resolved.) For measurement i used:
your scheduling latency benchmark:
http://www.efficios.com/pub/elc2010/wakeup-latency-0.1.tar.bz2 )
Please note that this test (wakeup-latency.c) uses a SIGEV_THREAD timer, for which the glibc implementation spawns a new thread every time the timer fires. Even though the glibc implementation should know better, it can be used as a good indication of the spread, as newly forked threads are put at the end of the runqueue with START_DEBIT. In addition, I recommend to also use the following test, which is a version of wakeup-latency.c I modified to use SIGEV_SIGNAL, to represent the timer latency without thread creation:
http://www.efficios.com/pub/sched-latency/wakeup-latency-signal-0.1.tar.bz2
I prefer to use both tests to figure out both the spread and timer signal latency.
Quoted 8 lines
In general, your patches have indeed produced a max-latency improvement
- and so has the simpler min_gran/3 patch too.So as Peter has suggested in his review, much of the same latency improvement can be gotten by the implicit /3 tune your patches do to min-granularity.
Quoted 6 lines
So perhaps it would be better to investigate/measure your series by making the min_gran/3 patch below your patch #1 - and thus your other changes (the
nr_runningdependency) could be evaluated relative to that.I.e. please re-phrase your series as: "what else does it give us beyond tuning down the minimum granularity to 33% of its current value?"
That's indeed the nice way to phrase the question. So the added value of my approach is that I don't change the granularity when there are 3 or less tasks running on the system. So, with Peter's approach, I expect that the system throughput will be lower in this scenario, but my approach should keep it at pretty much the same values as the vanilla kernel.
But you are right, I should put some performance measurements too. Let me do a few test runs (I plan to use tbench) and come back with the measurements with nr_running <= 3 for both Peter's approach and mine.
Thanks,
Mathieu
Quoted 2,555 lines
Your patches might have further merit than these numbers alone show - here i tried to limit my measurements to the measurements you yourself used. Maybe your approach can handle the granularity tradeoffs better in some other workload, etc.
Thanks,
Ingo
---------------------------->
vanilla (cced86a):maximum latency: 46980.9 µs
average latency: 7696.9 µs
missed timer events: 0
maximum latency: 35636.3 µs
average latency: 7736.6 µs
missed timer events: 0
maximum latency: 32219.6 µs
average latency: 7757.0 µsmathieu-dyn (cced86a+the-2-patches-in-this-thread):
maximum latency: 33999.4 µs
average latency: 9410.9 µs
missed timer events: 0
maximum latency: 26125.7 µs
average latency: 7083.2 µs
missed timer events: 0
maximum latency: 25971.5 µs
average latency: 6777.3 µs
missed timer events: 0peterz-min_gran/3 (cced86a+the-patch-attached-below):
maximum latency: 22366.3 µs
average latency: 7163.5 µs
missed timer events: 0
maximum latency: 15166.4 µs
average latency: 6788.6 µs
missed timer events: 0
maximum latency: 30573.8 µs
average latency: 6102.5 µs--- kernel/sched_fair.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)Index:
linux/kernel/sched_fair.c
===================================================================kernel/sched_fair.c +3
-3@@ -54,13 +54,13 @@ enum sched_tunable_scaling sysctl_sched_* Minimal preemption granularity for CPU-bound tasks: * (default: 2 msec * (1 + ilog(ncpus)), units: nanoseconds) */ -unsigned int sysctl_sched_min_granularity =2000000ULL ; -unsigned int normalized_sysctl_sched_min_granularity =2000000ULL ; +unsigned int sysctl_sched_min_granularity =750000ULL ; +unsigned int normalized_sysctl_sched_min_granularity =750000ULL ;/* * is kept at sysctl_sched_latency / sysctl_sched_min_granularity */ -static unsigned int sched_nr_latency =3 ; +static unsigned int sched_nr_latency =8 ;/* * After fork, child runs first. If set to 0 (default) then #
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.36-rc3
# Mon Sep 13 00:28:11 2010
#CONFIG_64BIT=y
#CONFIG_X86_32is not setCONFIG_X86_64=yCONFIG_X86=yCONFIG_INSTRUCTION_DECODER=yCONFIG_OUTPUT_FORMAT="elf64-x86-64"CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"CONFIG_GENERIC_CMOS_UPDATE=yCONFIG_CLOCKSOURCE_WATCHDOG=yCONFIG_GENERIC_CLOCKEVENTS=yCONFIG_GENERIC_CLOCKEVENTS_BROADCAST=yCONFIG_LOCKDEP_SUPPORT=yCONFIG_STACKTRACE_SUPPORT=yCONFIG_HAVE_LATENCYTOP_SUPPORT=yCONFIG_MMU=yCONFIG_ZONE_DMA=yCONFIG_NEED_DMA_MAP_STATE=yCONFIG_NEED_SG_DMA_LENGTH=yCONFIG_GENERIC_ISA_DMA=yCONFIG_GENERIC_IOMAP=yCONFIG_GENERIC_BUG=yCONFIG_GENERIC_BUG_RELATIVE_POINTERS=yCONFIG_GENERIC_HWEIGHT=yCONFIG_ARCH_MAY_HAVE_PC_FDC=y
#CONFIG_RWSEM_GENERIC_SPINLOCKis not setCONFIG_RWSEM_XCHGADD_ALGORITHM=yCONFIG_ARCH_HAS_CPU_IDLE_WAIT=yCONFIG_GENERIC_CALIBRATE_DELAY=yCONFIG_GENERIC_TIME_VSYSCALL=yCONFIG_ARCH_HAS_CPU_RELAX=yCONFIG_ARCH_HAS_DEFAULT_IDLE=yCONFIG_ARCH_HAS_CACHE_LINE_SIZE=yCONFIG_HAVE_SETUP_PER_CPU_AREA=yCONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=yCONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
#CONFIG_HAVE_CPUMASK_OF_CPU_MAPis not setCONFIG_ARCH_HIBERNATION_POSSIBLE=yCONFIG_ARCH_SUSPEND_POSSIBLE=yCONFIG_ZONE_DMA32=yCONFIG_ARCH_POPULATES_NODE_MAP=yCONFIG_AUDIT_ARCH=yCONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=yCONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=yCONFIG_HAVE_EARLY_RES=yCONFIG_GENERIC_HARDIRQS=yCONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=yCONFIG_GENERIC_IRQ_PROBE=yCONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi-fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11" #CONFIG_KTIME_SCALARis not setCONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"CONFIG_CONSTRUCTORS=y#
# General setup
#CONFIG_EXPERIMENTAL=yCONFIG_BROKEN_ON_SMP=yCONFIG_INIT_ENV_ARG_LIMIT=32CONFIG_CROSS_COMPILE=""CONFIG_LOCALVERSION=""CONFIG_LOCALVERSION_AUTO=yCONFIG_HAVE_KERNEL_GZIP=yCONFIG_HAVE_KERNEL_BZIP2=yCONFIG_HAVE_KERNEL_LZMA=yCONFIG_HAVE_KERNEL_LZO=yCONFIG_KERNEL_GZIP=y
#CONFIG_KERNEL_BZIP2is not set
#CONFIG_KERNEL_LZMAis not set
#CONFIG_KERNEL_LZOis not setCONFIG_SWAP=yCONFIG_SYSVIPC=yCONFIG_SYSVIPC_SYSCTL=yCONFIG_POSIX_MQUEUE=yCONFIG_POSIX_MQUEUE_SYSCTL=yCONFIG_BSD_PROCESS_ACCT=y
#CONFIG_BSD_PROCESS_ACCT_V3is not set
#CONFIG_TASKSTATSis not set
#CONFIG_AUDITis not set#
# RCU Subsystem
#CONFIG_TREE_RCU=y
#CONFIG_TINY_RCUis not set
#CONFIG_RCU_TRACEis not setCONFIG_RCU_FANOUT=64
#CONFIG_RCU_FANOUT_EXACTis not set
#CONFIG_TREE_RCU_TRACEis not set
#CONFIG_IKCONFIGis not setCONFIG_LOG_BUF_SHIFT=18CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
#CONFIG_CGROUPSis not setCONFIG_SYSFS_DEPRECATED=yCONFIG_SYSFS_DEPRECATED_V2=yCONFIG_RELAY=yCONFIG_NAMESPACES=y
#CONFIG_UTS_NSis not set
#CONFIG_IPC_NSis not set
#CONFIG_USER_NSis not set
#CONFIG_PID_NSis not set
#CONFIG_NET_NSis not setCONFIG_BLK_DEV_INITRD=yCONFIG_INITRAMFS_SOURCE=""CONFIG_RD_GZIP=yCONFIG_RD_BZIP2=yCONFIG_RD_LZMA=yCONFIG_RD_LZO=yCONFIG_CC_OPTIMIZE_FOR_SIZE=yCONFIG_SYSCTL=yCONFIG_ANON_INODES=y
#CONFIG_EMBEDDEDis not setCONFIG_UID16=yCONFIG_SYSCTL_SYSCALL=yCONFIG_KALLSYMS=y
#CONFIG_KALLSYMS_ALLis not setCONFIG_KALLSYMS_EXTRA_PASS=yCONFIG_HOTPLUG=yCONFIG_PRINTK=yCONFIG_BUG=yCONFIG_ELF_CORE=yCONFIG_PCSPKR_PLATFORM=yCONFIG_BASE_FULL=yCONFIG_FUTEX=yCONFIG_EPOLL=yCONFIG_SIGNALFD=yCONFIG_TIMERFD=yCONFIG_EVENTFD=yCONFIG_SHMEM=yCONFIG_AIO=yCONFIG_HAVE_PERF_EVENTS=y#
# Kernel Performance Events And Counters
#CONFIG_PERF_EVENTS=yCONFIG_PERF_COUNTERS=y
#CONFIG_DEBUG_PERF_USE_VMALLOCis not setCONFIG_VM_EVENT_COUNTERS=yCONFIG_PCI_QUIRKS=yCONFIG_SLUB_DEBUG=y
#CONFIG_COMPAT_BRKis not set
#CONFIG_SLABis not setCONFIG_SLUB=yCONFIG_PROFILING=yCONFIG_TRACEPOINTS=yCONFIG_OPROFILE=y
#CONFIG_OPROFILE_EVENT_MULTIPLEXis not setCONFIG_HAVE_OPROFILE=yCONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=yCONFIG_HAVE_IOREMAP_PROT=yCONFIG_HAVE_KPROBES=yCONFIG_HAVE_KRETPROBES=yCONFIG_HAVE_OPTPROBES=yCONFIG_HAVE_ARCH_TRACEHOOK=yCONFIG_HAVE_DMA_ATTRS=yCONFIG_HAVE_REGS_AND_STACK_ACCESS_API=yCONFIG_HAVE_DMA_API_DEBUG=yCONFIG_HAVE_HW_BREAKPOINT=yCONFIG_HAVE_MIXED_BREAKPOINTS_REGS=yCONFIG_HAVE_USER_RETURN_NOTIFIER=yCONFIG_HAVE_PERF_EVENTS_NMI=y#
# GCOV-based kernel profiling
#
#CONFIG_GCOV_KERNELis not set
#CONFIG_HAVE_GENERIC_DMA_COHERENTis not setCONFIG_SLABINFO=yCONFIG_RT_MUTEXES=yCONFIG_BASE_SMALL=0
#CONFIG_MODULESis not setCONFIG_BLOCK=yCONFIG_BLK_DEV_BSG=y
#CONFIG_BLK_DEV_INTEGRITYis not setCONFIG_BLOCK_COMPAT=y#
# IO Schedulers
#CONFIG_IOSCHED_NOOP=yCONFIG_IOSCHED_DEADLINE=yCONFIG_IOSCHED_CFQ=y
#CONFIG_DEFAULT_DEADLINEis not setCONFIG_DEFAULT_CFQ=y
#CONFIG_DEFAULT_NOOPis not setCONFIG_DEFAULT_IOSCHED="cfq"
#CONFIG_INLINE_SPIN_TRYLOCKis not set
#CONFIG_INLINE_SPIN_TRYLOCK_BHis not set #CONFIG_INLINE_SPIN_LOCKis not set
#CONFIG_INLINE_SPIN_LOCK_BHis not set
#CONFIG_INLINE_SPIN_LOCK_IRQis not set
#CONFIG_INLINE_SPIN_LOCK_IRQSAVEis not setCONFIG_INLINE_SPIN_UNLOCK=y
#CONFIG_INLINE_SPIN_UNLOCK_BHis not setCONFIG_INLINE_SPIN_UNLOCK_IRQ=y
#CONFIG_INLINE_SPIN_UNLOCK_IRQRESTOREis not set #CONFIG_INLINE_READ_TRYLOCKis not set
#CONFIG_INLINE_READ_LOCKis not set
#CONFIG_INLINE_READ_LOCK_BHis not set
#CONFIG_INLINE_READ_LOCK_IRQis not set
#CONFIG_INLINE_READ_LOCK_IRQSAVEis not setCONFIG_INLINE_READ_UNLOCK=y
#CONFIG_INLINE_READ_UNLOCK_BHis not setCONFIG_INLINE_READ_UNLOCK_IRQ=y
#CONFIG_INLINE_READ_UNLOCK_IRQRESTOREis not set #CONFIG_INLINE_WRITE_TRYLOCKis not set
#CONFIG_INLINE_WRITE_LOCKis not set
#CONFIG_INLINE_WRITE_LOCK_BHis not set
#CONFIG_INLINE_WRITE_LOCK_IRQis not set #CONFIG_INLINE_WRITE_LOCK_IRQSAVEis not setCONFIG_INLINE_WRITE_UNLOCK=y
#CONFIG_INLINE_WRITE_UNLOCK_BHis not setCONFIG_INLINE_WRITE_UNLOCK_IRQ=y
#CONFIG_INLINE_WRITE_UNLOCK_IRQRESTOREis not set #CONFIG_MUTEX_SPIN_ON_OWNERis not set
#CONFIG_FREEZERis not set#
# Processor type and features
#CONFIG_TICK_ONESHOT=yCONFIG_NO_HZ=yCONFIG_HIGH_RES_TIMERS=yCONFIG_GENERIC_CLOCKEVENTS_BUILD=y
#CONFIG_SMPis not set
#CONFIG_SPARSE_IRQis not setCONFIG_X86_MPPARSE=y
#CONFIG_X86_EXTENDED_PLATFORMis not setCONFIG_X86_SUPPORTS_MEMORY_FAILURE=yCONFIG_SCHED_OMIT_FRAME_POINTER=y
#CONFIG_PARAVIRT_GUESTis not setCONFIG_NO_BOOTMEM=y
#CONFIG_MEMTESTis not set
#CONFIG_MK8is not set
#CONFIG_MPSCis not setCONFIG_MCORE2=y
#CONFIG_MATOMis not set
#CONFIG_GENERIC_CPUis not setCONFIG_X86_CPU=yCONFIG_X86_INTERNODE_CACHE_SHIFT=6CONFIG_X86_CMPXCHG=yCONFIG_X86_L1_CACHE_SHIFT=6CONFIG_X86_XADD=yCONFIG_X86_WP_WORKS_OK=yCONFIG_X86_INTEL_USERCOPY=yCONFIG_X86_USE_PPRO_CHECKSUM=yCONFIG_X86_P6_NOP=yCONFIG_X86_TSC=yCONFIG_X86_CMPXCHG64=yCONFIG_X86_CMOV=yCONFIG_X86_MINIMUM_CPU_FAMILY=64CONFIG_X86_DEBUGCTLMSR=yCONFIG_CPU_SUP_INTEL=yCONFIG_CPU_SUP_AMD=yCONFIG_CPU_SUP_CENTAUR=yCONFIG_HPET_TIMER=yCONFIG_HPET_EMULATE_RTC=yCONFIG_DMI=yCONFIG_GART_IOMMU=yCONFIG_CALGARY_IOMMU=y
#CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULTis not set #CONFIG_AMD_IOMMUis not setCONFIG_SWIOTLB=yCONFIG_IOMMU_HELPER=y
#CONFIG_IOMMU_APIis not setCONFIG_NR_CPUS=1CONFIG_PREEMPT_NONE=y
#CONFIG_PREEMPT_VOLUNTARYis not set
#CONFIG_PREEMPTis not setCONFIG_X86_LOCAL_APIC=yCONFIG_X86_IO_APIC=y
#CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQSis not setCONFIG_X86_MCE=yCONFIG_X86_MCE_INTEL=y
#CONFIG_X86_MCE_AMDis not setCONFIG_X86_MCE_THRESHOLD=y
#CONFIG_X86_MCE_INJECTis not setCONFIG_X86_THERMAL_VECTOR=y
#CONFIG_I8Kis not set
#CONFIG_MICROCODEis not setCONFIG_X86_MSR=yCONFIG_X86_CPUID=yCONFIG_ARCH_PHYS_ADDR_T_64BIT=yCONFIG_DIRECT_GBPAGES=yCONFIG_ARCH_PROC_KCORE_TEXT=yCONFIG_ARCH_SPARSEMEM_DEFAULT=yCONFIG_ARCH_SPARSEMEM_ENABLE=yCONFIG_ARCH_SELECT_MEMORY_MODEL=yCONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000CONFIG_SELECT_MEMORY_MODEL=yCONFIG_SPARSEMEM_MANUAL=yCONFIG_SPARSEMEM=yCONFIG_HAVE_MEMORY_PRESENT=yCONFIG_SPARSEMEM_EXTREME=yCONFIG_SPARSEMEM_VMEMMAP_ENABLE=yCONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER=yCONFIG_SPARSEMEM_VMEMMAP=y
#CONFIG_MEMORY_HOTPLUGis not setCONFIG_PAGEFLAGS_EXTENDED=yCONFIG_SPLIT_PTLOCK_CPUS=4
#CONFIG_COMPACTIONis not setCONFIG_PHYS_ADDR_T_64BIT=yCONFIG_ZONE_DMA_FLAG=1CONFIG_BOUNCE=yCONFIG_VIRT_TO_BUS=y
#CONFIG_KSMis not setCONFIG_DEFAULT_MMAP_MIN_ADDR=4096CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
#CONFIG_MEMORY_FAILUREis not set
#CONFIG_X86_CHECK_BIOS_CORRUPTIONis not setCONFIG_X86_RESERVE_LOW_64K=yCONFIG_MTRR=y
#CONFIG_MTRR_SANITIZERis not setCONFIG_X86_PAT=yCONFIG_ARCH_USES_PG_UNCACHED=y
#CONFIG_EFIis not setCONFIG_SECCOMP=y
#CONFIG_CC_STACKPROTECTORis not set
#CONFIG_HZ_100is not setCONFIG_HZ_250=y
#CONFIG_HZ_300is not set
#CONFIG_HZ_1000is not setCONFIG_HZ=250CONFIG_SCHED_HRTICK=y
#CONFIG_KEXECis not set
#CONFIG_CRASH_DUMPis not setCONFIG_PHYSICAL_START=0x1000000CONFIG_RELOCATABLE=yCONFIG_PHYSICAL_ALIGN=0x1000000CONFIG_COMPAT_VDSO=y
#CONFIG_CMDLINE_BOOLis not setCONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y#
# Power management and ACPI options
#CONFIG_PM=y
#CONFIG_PM_DEBUGis not set
#CONFIG_SUSPENDis not set
#CONFIG_HIBERNATIONis not set
#CONFIG_PM_RUNTIMEis not setCONFIG_ACPI=yCONFIG_ACPI_PROCFS=yCONFIG_ACPI_PROCFS_POWER=y
#CONFIG_ACPI_POWER_METERis not setCONFIG_ACPI_SYSFS_POWER=y
#CONFIG_ACPI_EC_DEBUGFSis not set
#CONFIG_ACPI_PROC_EVENTis not setCONFIG_ACPI_AC=yCONFIG_ACPI_BATTERY=yCONFIG_ACPI_BUTTON=yCONFIG_ACPI_VIDEO=yCONFIG_ACPI_FAN=yCONFIG_ACPI_DOCK=yCONFIG_ACPI_PROCESSOR=y
#CONFIG_ACPI_PROCESSOR_AGGREGATORis not setCONFIG_ACPI_THERMAL=y
#CONFIG_ACPI_CUSTOM_DSDTis not setCONFIG_ACPI_BLACKLIST_YEAR=0
#CONFIG_ACPI_DEBUGis not set
#CONFIG_ACPI_PCI_SLOTis not setCONFIG_X86_PM_TIMER=yCONFIG_ACPI_CONTAINER=y
#CONFIG_ACPI_SBSis not set
#CONFIG_ACPI_HEDis not set
#CONFIG_ACPI_APEIis not set
#CONFIG_SFIis not set#
# CPU Frequency scaling
#CONFIG_CPU_FREQ=yCONFIG_CPU_FREQ_TABLE=yCONFIG_CPU_FREQ_DEBUG=y
#CONFIG_CPU_FREQ_STATis not set
#CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCEis not set #CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACEis not setCONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
#CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVEis not setCONFIG_CPU_FREQ_GOV_PERFORMANCE=yCONFIG_CPU_FREQ_GOV_POWERSAVE=yCONFIG_CPU_FREQ_GOV_USERSPACE=yCONFIG_CPU_FREQ_GOV_ONDEMAND=y
#CONFIG_CPU_FREQ_GOV_CONSERVATIVEis not set#
# CPUFreq processor drivers
#
#CONFIG_X86_PCC_CPUFREQis not setCONFIG_X86_ACPI_CPUFREQ=yCONFIG_X86_POWERNOW_K8=yCONFIG_X86_SPEEDSTEP_CENTRINO=y
#CONFIG_X86_P4_CLOCKMODis not set#
# shared options # # CONFIG_X86_SPEEDSTEP_LIB is not set CONFIG_CPU_IDLE=y CONFIG_CPU_IDLE_GOV_LADDER=y CONFIG_CPU_IDLE_GOV_MENU=y # CONFIG_INTEL_IDLE is not set#
# Memory power savings
#
#CONFIG_I7300_IDLEis not set#
# Bus options (PCI etc.)
#CONFIG_PCI=yCONFIG_PCI_DIRECT=yCONFIG_PCI_MMCONFIG=yCONFIG_PCI_DOMAINS=y
#CONFIG_PCI_CNB20LE_QUIRKis not set
#CONFIG_DMARis not set
#CONFIG_INTR_REMAPis not setCONFIG_PCIEPORTBUS=y
#CONFIG_HOTPLUG_PCI_PCIEis not setCONFIG_PCIEAER=y
#CONFIG_PCIE_ECRCis not set
#CONFIG_PCIEAER_INJECTis not setCONFIG_PCIEASPM=y
#CONFIG_PCIEASPM_DEBUGis not setCONFIG_ARCH_SUPPORTS_MSI=yCONFIG_PCI_MSI=y
#CONFIG_PCI_DEBUGis not set
#CONFIG_PCI_STUBis not set
#CONFIG_HT_IRQis not set
#CONFIG_PCI_IOVis not setCONFIG_PCI_IOAPIC=yCONFIG_ISA_DMA_API=yCONFIG_K8_NB=y
#CONFIG_PCCARDis not setCONFIG_HOTPLUG_PCI=y
#CONFIG_HOTPLUG_PCI_FAKEis not set
#CONFIG_HOTPLUG_PCI_ACPIis not set
#CONFIG_HOTPLUG_PCI_CPCIis not set
#CONFIG_HOTPLUG_PCI_SHPCis not set#
# Executable file formats / Emulations
#CONFIG_BINFMT_ELF=yCONFIG_COMPAT_BINFMT_ELF=y
#CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERSis not set
#CONFIG_HAVE_AOUTis not setCONFIG_BINFMT_MISC=yCONFIG_IA32_EMULATION=y
#CONFIG_IA32_AOUTis not setCONFIG_COMPAT=yCONFIG_COMPAT_FOR_U64_ALIGNMENT=yCONFIG_SYSVIPC_COMPAT=yCONFIG_NET=y#
# Networking options
#CONFIG_PACKET=yCONFIG_UNIX=yCONFIG_XFRM=y
#CONFIG_XFRM_USERis not set
#CONFIG_XFRM_SUB_POLICYis not set
#CONFIG_XFRM_MIGRATEis not set
#CONFIG_XFRM_STATISTICSis not set
#CONFIG_NET_KEYis not setCONFIG_INET=yCONFIG_IP_MULTICAST=yCONFIG_IP_ADVANCED_ROUTER=yCONFIG_ASK_IP_FIB_HASH=y
#CONFIG_IP_FIB_TRIEis not setCONFIG_IP_FIB_HASH=yCONFIG_IP_MULTIPLE_TABLES=yCONFIG_IP_ROUTE_MULTIPATH=yCONFIG_IP_ROUTE_VERBOSE=y
#CONFIG_IP_PNPis not set
#CONFIG_NET_IPIPis not set
#CONFIG_NET_IPGREis not setCONFIG_IP_MROUTE=y
#CONFIG_IP_MROUTE_MULTIPLE_TABLESis not setCONFIG_IP_PIMSM_V1=yCONFIG_IP_PIMSM_V2=y
#CONFIG_ARPDis not setCONFIG_SYN_COOKIES=y
#CONFIG_INET_AHis not set
#CONFIG_INET_ESPis not set
#CONFIG_INET_IPCOMPis not set
#CONFIG_INET_XFRM_TUNNELis not setCONFIG_INET_TUNNEL=yCONFIG_INET_XFRM_MODE_TRANSPORT=yCONFIG_INET_XFRM_MODE_TUNNEL=y
#CONFIG_INET_XFRM_MODE_BEETis not set
#CONFIG_INET_LROis not set
#CONFIG_INET_DIAGis not set
#CONFIG_TCP_CONG_ADVANCEDis not setCONFIG_TCP_CONG_CUBIC=yCONFIG_DEFAULT_TCP_CONG="cubic"
#CONFIG_TCP_MD5SIGis not setCONFIG_IPV6=y
#CONFIG_IPV6_PRIVACYis not set
#CONFIG_IPV6_ROUTER_PREFis not set
#CONFIG_IPV6_OPTIMISTIC_DADis not set
#CONFIG_INET6_AHis not set
#CONFIG_INET6_ESPis not set
#CONFIG_INET6_IPCOMPis not set
#CONFIG_IPV6_MIP6is not set
#CONFIG_INET6_XFRM_TUNNELis not set
#CONFIG_INET6_TUNNELis not set
#CONFIG_INET6_XFRM_MODE_TRANSPORTis not set #CONFIG_INET6_XFRM_MODE_TUNNELis not set
#CONFIG_INET6_XFRM_MODE_BEETis not set
#CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATIONis not setCONFIG_IPV6_SIT=y
#CONFIG_IPV6_SIT_6RDis not setCONFIG_IPV6_NDISC_NODETYPE=y
#CONFIG_IPV6_TUNNELis not set
#CONFIG_IPV6_MULTIPLE_TABLESis not set
#CONFIG_IPV6_MROUTEis not set
#CONFIG_NETLABELis not setCONFIG_NETWORK_SECMARK=y
#CONFIG_NETWORK_PHY_TIMESTAMPINGis not setCONFIG_NETFILTER=y
#CONFIG_NETFILTER_DEBUGis not set
#CONFIG_NETFILTER_ADVANCEDis not set#
# Core Netfilter Configuration
#
#CONFIG_NETFILTER_NETLINK_LOGis not setCONFIG_NF_CONNTRACK=y
#CONFIG_NF_CONNTRACK_SECMARKis not setCONFIG_NF_CONNTRACK_FTP=y
#CONFIG_NF_CONNTRACK_IRCis not set
#CONFIG_NF_CONNTRACK_SIPis not set
#CONFIG_NF_CT_NETLINKis not setCONFIG_NETFILTER_XTABLES=y#
# Xtables combined modules
#CONFIG_NETFILTER_XT_MARK=y#
# Xtables targets
#
#CONFIG_NETFILTER_XT_TARGET_NFLOGis not setCONFIG_NETFILTER_XT_TARGET_SECMARK=y
#CONFIG_NETFILTER_XT_TARGET_TCPMSSis not set#
# Xtables matches
#CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y
#CONFIG_NETFILTER_XT_MATCH_POLICYis not setCONFIG_NETFILTER_XT_MATCH_STATE=y
#CONFIG_IP_VSis not set#
# IP: Netfilter Configuration
#CONFIG_NF_DEFRAG_IPV4=yCONFIG_NF_CONNTRACK_IPV4=yCONFIG_NF_CONNTRACK_PROC_COMPAT=yCONFIG_IP_NF_IPTABLES=yCONFIG_IP_NF_FILTER=yCONFIG_IP_NF_TARGET_REJECT=yCONFIG_IP_NF_TARGET_LOG=yCONFIG_IP_NF_TARGET_ULOG=yCONFIG_NF_NAT=yCONFIG_NF_NAT_NEEDED=yCONFIG_IP_NF_TARGET_MASQUERADE=yCONFIG_NF_NAT_FTP=y
#CONFIG_NF_NAT_IRCis not set
#CONFIG_NF_NAT_TFTPis not set
#CONFIG_NF_NAT_AMANDAis not set
#CONFIG_NF_NAT_PPTPis not set
#CONFIG_NF_NAT_H323is not set
#CONFIG_NF_NAT_SIPis not setCONFIG_IP_NF_MANGLE=y#
# IPv6: Netfilter Configuration
#CONFIG_NF_CONNTRACK_IPV6=yCONFIG_IP6_NF_IPTABLES=yCONFIG_IP6_NF_MATCH_IPV6HEADER=yCONFIG_IP6_NF_TARGET_LOG=yCONFIG_IP6_NF_FILTER=yCONFIG_IP6_NF_TARGET_REJECT=y
#CONFIG_IP6_NF_MANGLEis not set
#CONFIG_IP_DCCPis not set
#CONFIG_IP_SCTPis not set
#CONFIG_RDSis not set
#CONFIG_TIPCis not set
#CONFIG_ATMis not set
#CONFIG_L2TPis not set
#CONFIG_BRIDGEis not set
#CONFIG_NET_DSAis not set
#CONFIG_VLAN_8021Qis not set
#CONFIG_DECNETis not setCONFIG_LLC=y
#CONFIG_LLC2is not set
#CONFIG_IPXis not set
#CONFIG_ATALKis not set
#CONFIG_X25is not set
#CONFIG_LAPBis not set
#CONFIG_ECONETis not set
#CONFIG_WAN_ROUTERis not set
#CONFIG_PHONETis not set
#CONFIG_IEEE802154is not setCONFIG_NET_SCHED=y#
# Queueing/Scheduling
#
#CONFIG_NET_SCH_CBQis not set
#CONFIG_NET_SCH_HTBis not set
#CONFIG_NET_SCH_HFSCis not set
#CONFIG_NET_SCH_PRIOis not set
#CONFIG_NET_SCH_MULTIQis not set
#CONFIG_NET_SCH_REDis not set
#CONFIG_NET_SCH_SFQis not set
#CONFIG_NET_SCH_TEQLis not set
#CONFIG_NET_SCH_TBFis not set
#CONFIG_NET_SCH_GREDis not set
#CONFIG_NET_SCH_DSMARKis not set
#CONFIG_NET_SCH_NETEMis not set
#CONFIG_NET_SCH_DRRis not set
#CONFIG_NET_SCH_INGRESSis not set#
# Classification
#CONFIG_NET_CLS=y
#CONFIG_NET_CLS_BASICis not set
#CONFIG_NET_CLS_TCINDEXis not set
#CONFIG_NET_CLS_ROUTE4is not set
#CONFIG_NET_CLS_FWis not set
#CONFIG_NET_CLS_U32is not set
#CONFIG_NET_CLS_RSVPis not set
#CONFIG_NET_CLS_RSVP6is not set
#CONFIG_NET_CLS_FLOWis not setCONFIG_NET_EMATCH=yCONFIG_NET_EMATCH_STACK=32
#CONFIG_NET_EMATCH_CMPis not set
#CONFIG_NET_EMATCH_NBYTEis not set
#CONFIG_NET_EMATCH_U32is not set
#CONFIG_NET_EMATCH_METAis not set
#CONFIG_NET_EMATCH_TEXTis not setCONFIG_NET_CLS_ACT=yCONFIG_NET_ACT_POLICE=y
#CONFIG_NET_ACT_GACTis not set
#CONFIG_NET_ACT_MIRREDis not set
#CONFIG_NET_ACT_IPTis not set
#CONFIG_NET_ACT_NATis not set
#CONFIG_NET_ACT_PEDITis not set
#CONFIG_NET_ACT_SIMPis not set
#CONFIG_NET_ACT_SKBEDITis not setCONFIG_NET_SCH_FIFO=y
#CONFIG_DCBis not set
#CONFIG_DNS_RESOLVERis not set#
# Network testing
#
#CONFIG_NET_PKTGENis not set
#CONFIG_NET_DROP_MONITORis not set
#CONFIG_HAMRADIOis not set
#CONFIG_CANis not set
#CONFIG_IRDAis not set
#CONFIG_BTis not set
#CONFIG_AF_RXRPCis not setCONFIG_FIB_RULES=yCONFIG_WIRELESS=y
#CONFIG_CFG80211is not set
#CONFIG_LIB80211is not set#
# CFG80211 needs to be enabled for MAC80211
##
# Some wireless drivers require a rate control algorithm #
#CONFIG_WIMAXis not set
#CONFIG_RFKILLis not set
#CONFIG_NET_9Pis not set
#CONFIG_CAIFis not set#
# Device Drivers
##
# Generic Driver Options
#CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
#CONFIG_DEVTMPFSis not setCONFIG_STANDALONE=yCONFIG_PREVENT_FIRMWARE_BUILD=yCONFIG_FW_LOADER=yCONFIG_FIRMWARE_IN_KERNEL=yCONFIG_EXTRA_FIRMWARE=""
#CONFIG_DEBUG_DRIVERis not set
#CONFIG_DEBUG_DEVRESis not set
#CONFIG_SYS_HYPERVISORis not set
#CONFIG_CONNECTORis not set
#CONFIG_MTDis not set
#CONFIG_PARPORTis not setCONFIG_PNP=yCONFIG_PNP_DEBUG_MESSAGES=y#
# Protocols
#CONFIG_PNPACPI=yCONFIG_BLK_DEV=y
#CONFIG_BLK_DEV_FDis not set
#CONFIG_BLK_CPQ_DAis not set
#CONFIG_BLK_CPQ_CISS_DAis not set
#CONFIG_BLK_DEV_DAC960is not set
#CONFIG_BLK_DEV_UMEMis not set
#CONFIG_BLK_DEV_COW_COMMONis not set
#CONFIG_BLK_DEV_LOOPis not set#
# DRBD disabled becausePROC_FS, INET or CONNECTOR not selected #
#CONFIG_BLK_DEV_NBDis not set
#CONFIG_BLK_DEV_SX8is not set
#CONFIG_BLK_DEV_UBis not setCONFIG_BLK_DEV_RAM=yCONFIG_BLK_DEV_RAM_COUNT=16CONFIG_BLK_DEV_RAM_SIZE=16384
#CONFIG_BLK_DEV_XIPis not set
#CONFIG_CDROM_PKTCDVDis not set
#CONFIG_ATA_OVER_ETHis not set
#CONFIG_BLK_DEV_HDis not setCONFIG_MISC_DEVICES=y
#CONFIG_AD525X_DPOTis not set
#CONFIG_IBM_ASMis not set
#CONFIG_PHANTOMis not set
#CONFIG_SGI_IOC4is not set
#CONFIG_TIFM_COREis not set
#CONFIG_ICS932S401is not set
#CONFIG_ENCLOSURE_SERVICESis not set
#CONFIG_CS5535_MFGPTis not set
#CONFIG_HP_ILOis not set
#CONFIG_ISL29003is not set
#CONFIG_SENSORS_TSL2550is not set
#CONFIG_SENSORS_BH1780is not set
#CONFIG_HMC6352is not set
#CONFIG_DS1682is not set
#CONFIG_VMWARE_BALLOONis not set
#CONFIG_BMP085is not set
#CONFIG_C2PORTis not set#
# EEPROM support
#
#CONFIG_EEPROM_AT24is not set
#CONFIG_EEPROM_LEGACYis not set
#CONFIG_EEPROM_MAX6875is not set
#CONFIG_EEPROM_93CX6is not set
#CONFIG_CB710_COREis not setCONFIG_HAVE_IDE=y
#CONFIG_IDEis not set#
# SCSI device support
#CONFIG_SCSI_MOD=y
#CONFIG_RAID_ATTRSis not setCONFIG_SCSI=yCONFIG_SCSI_DMA=y
#CONFIG_SCSI_TGTis not setCONFIG_SCSI_NETLINK=y
#CONFIG_SCSI_PROC_FSis not set#
# SCSI support type (disk, tape, CD-ROM)
#CONFIG_BLK_DEV_SD=y
#CONFIG_CHR_DEV_STis not set
#CONFIG_CHR_DEV_OSSTis not setCONFIG_BLK_DEV_SR=y
#CONFIG_BLK_DEV_SR_VENDORis not setCONFIG_CHR_DEV_SG=y
#CONFIG_CHR_DEV_SCHis not setCONFIG_SCSI_MULTI_LUN=y
#CONFIG_SCSI_CONSTANTSis not set
#CONFIG_SCSI_LOGGINGis not set
#CONFIG_SCSI_SCAN_ASYNCis not set#
# SCSI Transports
#
#CONFIG_SCSI_SPI_ATTRSis not setCONFIG_SCSI_FC_ATTRS=y
#CONFIG_SCSI_ISCSI_ATTRSis not set
#CONFIG_SCSI_SAS_ATTRSis not set
#CONFIG_SCSI_SAS_LIBSASis not set
#CONFIG_SCSI_SRP_ATTRSis not setCONFIG_SCSI_LOWLEVEL=y
#CONFIG_ISCSI_TCPis not set
#CONFIG_ISCSI_BOOT_SYSFSis not set
#CONFIG_SCSI_CXGB3_ISCSIis not set
#CONFIG_SCSI_BNX2_ISCSIis not set
#CONFIG_BE2ISCSIis not set
#CONFIG_BLK_DEV_3W_XXXX_RAIDis not set
#CONFIG_SCSI_HPSAis not set
#CONFIG_SCSI_3W_9XXXis not set
#CONFIG_SCSI_3W_SASis not set
#CONFIG_SCSI_ACARDis not set
#CONFIG_SCSI_AACRAIDis not set
#CONFIG_SCSI_AIC7XXXis not set
#CONFIG_SCSI_AIC7XXX_OLDis not set
#CONFIG_SCSI_AIC79XXis not set
#CONFIG_SCSI_AIC94XXis not set
#CONFIG_SCSI_MVSASis not set
#CONFIG_SCSI_DPT_I2Ois not set
#CONFIG_SCSI_ADVANSYSis not set
#CONFIG_SCSI_ARCMSRis not set
#CONFIG_MEGARAID_NEWGENis not set
#CONFIG_MEGARAID_LEGACYis not set
#CONFIG_MEGARAID_SASis not set
#CONFIG_SCSI_MPT2SASis not set
#CONFIG_SCSI_HPTIOPis not set
#CONFIG_SCSI_BUSLOGICis not set
#CONFIG_VMWARE_PVSCSIis not set
#CONFIG_LIBFCis not set
#CONFIG_LIBFCOEis not set
#CONFIG_FCOEis not set
#CONFIG_FCOE_FNICis not set
#CONFIG_SCSI_DMX3191Dis not set
#CONFIG_SCSI_EATAis not set
#CONFIG_SCSI_FUTURE_DOMAINis not set
#CONFIG_SCSI_GDTHis not set
#CONFIG_SCSI_IPSis not set
#CONFIG_SCSI_INITIOis not set
#CONFIG_SCSI_INIA100is not set
#CONFIG_SCSI_STEXis not set
#CONFIG_SCSI_SYM53C8XX_2is not set
#CONFIG_SCSI_IPRis not set
#CONFIG_SCSI_QLOGIC_1280is not set
#CONFIG_SCSI_QLA_FCis not set
#CONFIG_SCSI_QLA_ISCSIis not set
#CONFIG_SCSI_LPFCis not set
#CONFIG_SCSI_DC395xis not set
#CONFIG_SCSI_DC390Tis not set
#CONFIG_SCSI_DEBUGis not set
#CONFIG_SCSI_PMCRAIDis not set
#CONFIG_SCSI_PM8001is not set
#CONFIG_SCSI_SRPis not set
#CONFIG_SCSI_BFA_FCis not set
#CONFIG_SCSI_DHis not set
#CONFIG_SCSI_OSD_INITIATORis not setCONFIG_ATA=y
#CONFIG_ATA_NONSTANDARDis not setCONFIG_ATA_VERBOSE_ERROR=yCONFIG_ATA_ACPI=yCONFIG_SATA_PMP=y#
# Controllers with non-SFF native interface
#CONFIG_SATA_AHCI=y
#CONFIG_SATA_AHCI_PLATFORMis not set
#CONFIG_SATA_INIC162Xis not set
#CONFIG_SATA_SIL24is not setCONFIG_ATA_SFF=y#
# SFF controllers with custom DMA interface
#
#CONFIG_PDC_ADMAis not set
#CONFIG_SATA_QSTORis not set
#CONFIG_SATA_SX4is not setCONFIG_ATA_BMDMA=y#
# SATA SFF controllers with BMDMA
#CONFIG_ATA_PIIX=y
#CONFIG_SATA_MVis not set
#CONFIG_SATA_NVis not set
#CONFIG_SATA_PROMISEis not set
#CONFIG_SATA_SILis not set
#CONFIG_SATA_SISis not set
#CONFIG_SATA_SVWis not set
#CONFIG_SATA_ULIis not set
#CONFIG_SATA_VIAis not set
#CONFIG_SATA_VITESSEis not set#
# PATA SFF controllers with BMDMA
#
#CONFIG_PATA_ALIis not setCONFIG_PATA_AMD=y
#CONFIG_PATA_ARTOPis not set
#CONFIG_PATA_ATIIXPis not set
#CONFIG_PATA_ATP867Xis not set
#CONFIG_PATA_CMD64Xis not set
#CONFIG_PATA_CS5520is not set
#CONFIG_PATA_CS5530is not set
#CONFIG_PATA_CYPRESSis not set
#CONFIG_PATA_EFARis not set
#CONFIG_PATA_HPT366is not set
#CONFIG_PATA_HPT37Xis not set
#CONFIG_PATA_HPT3X2Nis not set
#CONFIG_PATA_HPT3X3is not set
#CONFIG_PATA_IT8213is not set
#CONFIG_PATA_IT821Xis not set
#CONFIG_PATA_JMICRONis not set
#CONFIG_PATA_MARVELLis not set
#CONFIG_PATA_NETCELLis not set
#CONFIG_PATA_NINJA32is not set
#CONFIG_PATA_NS87415is not set
#CONFIG_PATA_OLDPIIXis not set
#CONFIG_PATA_OPTIDMAis not set
#CONFIG_PATA_PDC2027Xis not set
#CONFIG_PATA_PDC_OLDis not set
#CONFIG_PATA_RADISYSis not set
#CONFIG_PATA_RDCis not set
#CONFIG_PATA_SC1200is not set
#CONFIG_PATA_SCHis not set
#CONFIG_PATA_SERVERWORKSis not set
#CONFIG_PATA_SIL680is not set
#CONFIG_PATA_SISis not set
#CONFIG_PATA_TOSHIBAis not set
#CONFIG_PATA_TRIFLEXis not set
#CONFIG_PATA_VIAis not set
#CONFIG_PATA_WINBONDis not set#
# PIO-only SFF controllers
#
#CONFIG_PATA_CMD640_PCIis not set
#CONFIG_PATA_MPIIXis not set
#CONFIG_PATA_NS87410is not set
#CONFIG_PATA_OPTIis not set
#CONFIG_PATA_RZ1000is not set#
# Generic fallback / legacy drivers
#
#CONFIG_PATA_ACPIis not set
#CONFIG_ATA_GENERICis not set
#CONFIG_PATA_LEGACYis not setCONFIG_MD=yCONFIG_BLK_DEV_MD=yCONFIG_MD_AUTODETECT=yCONFIG_MD_LINEAR=yCONFIG_MD_RAID0=y
#CONFIG_MD_RAID1is not set
#CONFIG_MD_RAID10is not set
#CONFIG_MD_RAID456is not set
#CONFIG_MD_MULTIPATHis not set
#CONFIG_MD_FAULTYis not setCONFIG_BLK_DEV_DM=y
#CONFIG_DM_DEBUGis not set
#CONFIG_DM_CRYPTis not setCONFIG_DM_SNAPSHOT=yCONFIG_DM_MIRROR=y
#CONFIG_DM_LOG_USERSPACEis not setCONFIG_DM_ZERO=y
#CONFIG_DM_MULTIPATHis not set
#CONFIG_DM_DELAYis not set
#CONFIG_DM_UEVENTis not set
#CONFIG_FUSIONis not set#
# IEEE 1394 (FireWire) support
##
# You can enable one or both FireWire driver stacks. ##
# The newer stack is recommended.
#
#CONFIG_FIREWIREis not set
#CONFIG_IEEE1394is not set
#CONFIG_FIREWIRE_NOSYis not set
#CONFIG_I2Ois not set
#CONFIG_MACINTOSH_DRIVERSis not setCONFIG_NETDEVICES=y
#CONFIG_IFBis not set
#CONFIG_DUMMYis not set
#CONFIG_BONDINGis not set
#CONFIG_MACVLANis not set
#CONFIG_EQUALIZERis not set
#CONFIG_TUNis not set
#CONFIG_VETHis not set
#CONFIG_NET_SB1000is not set
#CONFIG_ARCNETis not set
#CONFIG_PHYLIBis not setCONFIG_NET_ETHERNET=y
#CONFIG_MIIis not set
#CONFIG_HAPPYMEALis not set
#CONFIG_SUNGEMis not set
#CONFIG_CASSINIis not setCONFIG_NET_VENDOR_3COM=y
#CONFIG_VORTEXis not set
#CONFIG_TYPHOONis not set
#CONFIG_ETHOCis not set
#CONFIG_DNETis not setCONFIG_NET_TULIP=y
#CONFIG_DE2104Xis not set
#CONFIG_TULIPis not set
#CONFIG_DE4X5is not set
#CONFIG_WINBOND_840is not set
#CONFIG_DM9102is not set
#CONFIG_ULI526Xis not set
#CONFIG_HP100is not set
#CONFIG_IBM_NEW_EMAC_ZMIIis not set
#CONFIG_IBM_NEW_EMAC_RGMIIis not set
#CONFIG_IBM_NEW_EMAC_TAHis not set
#CONFIG_IBM_NEW_EMAC_EMAC4is not set
#CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRLis not set #CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTATis not set #CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERRis not setCONFIG_NET_PCI=y
#CONFIG_PCNET32is not set
#CONFIG_AMD8111_ETHis not set
#CONFIG_ADAPTEC_STARFIREis not set
#CONFIG_KSZ884X_PCIis not set
#CONFIG_B44is not setCONFIG_FORCEDETH=y
#CONFIG_E100is not set
#CONFIG_FEALNXis not set
#CONFIG_NATSEMIis not set
#CONFIG_NE2K_PCIis not set
#CONFIG_8139CPis not set
#CONFIG_8139TOOis not set
#CONFIG_R6040is not set
#CONFIG_SIS900is not set
#CONFIG_EPIC100is not set
#CONFIG_SMSC9420is not set
#CONFIG_SUNDANCEis not set
#CONFIG_TLANis not set
#CONFIG_KS8851_MLLis not set
#CONFIG_VIA_RHINEis not set
#CONFIG_SC92031is not set
#CONFIG_ATL2is not setCONFIG_NETDEV_1000=y
#CONFIG_ACENICis not set
#CONFIG_DL2Kis not setCONFIG_E1000=yCONFIG_E1000E=y
#CONFIG_IP1000is not setCONFIG_IGB=y
#CONFIG_IGBVFis not set
#CONFIG_NS83820is not set
#CONFIG_HAMACHIis not set
#CONFIG_YELLOWFINis not set
#CONFIG_R8169is not set
#CONFIG_SIS190is not set
#CONFIG_SKGEis not set
#CONFIG_SKY2is not set
#CONFIG_VIA_VELOCITYis not set
#CONFIG_TIGON3is not set
#CONFIG_BNX2is not set
#CONFIG_CNICis not set
#CONFIG_QLA3XXXis not set
#CONFIG_ATL1is not set
#CONFIG_ATL1Eis not set
#CONFIG_ATL1Cis not set
#CONFIG_JMEis not setCONFIG_NETDEV_10000=y
#CONFIG_CHELSIO_T1is not setCONFIG_CHELSIO_T3_DEPENDS=y
#CONFIG_CHELSIO_T3is not setCONFIG_CHELSIO_T4_DEPENDS=y
#CONFIG_CHELSIO_T4is not setCONFIG_CHELSIO_T4VF_DEPENDS=y
#CONFIG_CHELSIO_T4VFis not set
#CONFIG_ENICis not set
#CONFIG_IXGBEis not set
#CONFIG_IXGBEVFis not set
#CONFIG_IXGBis not set
#CONFIG_S2IOis not set
#CONFIG_VXGEis not set
#CONFIG_MYRI10GEis not set
#CONFIG_NETXEN_NICis not set
#CONFIG_NIUis not set
#CONFIG_MLX4_ENis not set
#CONFIG_MLX4_COREis not set
#CONFIG_TEHUTIis not set
#CONFIG_BNX2Xis not set
#CONFIG_QLCNICis not set
#CONFIG_QLGEis not set
#CONFIG_SFCis not set
#CONFIG_BE2NETis not setCONFIG_TR=y
#CONFIG_IBMOLis not set
#CONFIG_3C359is not set
#CONFIG_TMS380TRis not setCONFIG_WLAN=y
#CONFIG_AIROis not set
#CONFIG_ATMELis not set
#CONFIG_PRISM54is not set
#CONFIG_USB_ZD1201is not set
#CONFIG_HOSTAPis not set#
# Enable WiMAX (Networking options) to see the WiMAX drivers ##
# USB Network Adapters
#
#CONFIG_USB_CATCis not set
#CONFIG_USB_KAWETHis not set
#CONFIG_USB_PEGASUSis not set
#CONFIG_USB_RTL8150is not set
#CONFIG_USB_USBNETis not set
#CONFIG_USB_IPHETHis not set
#CONFIG_WANis not set#
# CAIF transport drivers
#CONFIG_FDDI=y
#CONFIG_DEFXXis not set
#CONFIG_SKFPis not set
#CONFIG_HIPPIis not set
#CONFIG_PPPis not set
#CONFIG_SLIPis not set
#CONFIG_NET_FCis not set
#CONFIG_NETCONSOLEis not set
#CONFIG_NETPOLLis not set
#CONFIG_NET_POLL_CONTROLLERis not set
#CONFIG_VMXNET3is not set
#CONFIG_ISDNis not set
#CONFIG_PHONEis not set#
# Input device support
#CONFIG_INPUT=yCONFIG_INPUT_FF_MEMLESS=y
#CONFIG_INPUT_POLLDEVis not set
#CONFIG_INPUT_SPARSEKMAPis not set#
# Userland interfaces
#CONFIG_INPUT_MOUSEDEV=y
#CONFIG_INPUT_MOUSEDEV_PSAUXis not setCONFIG_INPUT_MOUSEDEV_SCREEN_X=1024CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
#CONFIG_INPUT_JOYDEVis not setCONFIG_INPUT_EVDEV=y
#CONFIG_INPUT_EVBUGis not set#
# Input Device Drivers
#CONFIG_INPUT_KEYBOARD=y
#CONFIG_KEYBOARD_ADP5588is not setCONFIG_KEYBOARD_ATKBD=y
#CONFIG_KEYBOARD_QT2160is not set
#CONFIG_KEYBOARD_LKKBDis not set
#CONFIG_KEYBOARD_TCA6416is not set
#CONFIG_KEYBOARD_MAX7359is not set
#CONFIG_KEYBOARD_MCSis not set
#CONFIG_KEYBOARD_NEWTONis not set
#CONFIG_KEYBOARD_OPENCORESis not set
#CONFIG_KEYBOARD_STOWAWAYis not set
#CONFIG_KEYBOARD_SUNKBDis not set
#CONFIG_KEYBOARD_XTKBDis not setCONFIG_INPUT_MOUSE=yCONFIG_MOUSE_PS2=yCONFIG_MOUSE_PS2_ALPS=yCONFIG_MOUSE_PS2_LOGIPS2PP=yCONFIG_MOUSE_PS2_SYNAPTICS=yCONFIG_MOUSE_PS2_LIFEBOOK=yCONFIG_MOUSE_PS2_TRACKPOINT=y
#CONFIG_MOUSE_PS2_ELANTECHis not set
#CONFIG_MOUSE_PS2_SENTELICis not set
#CONFIG_MOUSE_PS2_TOUCHKITis not set
#CONFIG_MOUSE_SERIALis not set
#CONFIG_MOUSE_APPLETOUCHis not set
#CONFIG_MOUSE_BCM5974is not set
#CONFIG_MOUSE_VSXXXAAis not set
#CONFIG_MOUSE_SYNAPTICS_I2Cis not setCONFIG_INPUT_JOYSTICK=y
#CONFIG_JOYSTICK_ANALOGis not set
#CONFIG_JOYSTICK_A3Dis not set
#CONFIG_JOYSTICK_ADIis not set
#CONFIG_JOYSTICK_COBRAis not set
#CONFIG_JOYSTICK_GF2Kis not set
#CONFIG_JOYSTICK_GRIPis not set
#CONFIG_JOYSTICK_GRIP_MPis not set
#CONFIG_JOYSTICK_GUILLEMOTis not set
#CONFIG_JOYSTICK_INTERACTis not set
#CONFIG_JOYSTICK_SIDEWINDERis not set
#CONFIG_JOYSTICK_TMDCis not set
#CONFIG_JOYSTICK_IFORCEis not set
#CONFIG_JOYSTICK_WARRIORis not set
#CONFIG_JOYSTICK_MAGELLANis not set
#CONFIG_JOYSTICK_SPACEORBis not set
#CONFIG_JOYSTICK_SPACEBALLis not set
#CONFIG_JOYSTICK_STINGERis not set
#CONFIG_JOYSTICK_TWIDJOYis not set
#CONFIG_JOYSTICK_ZHENHUAis not set
#CONFIG_JOYSTICK_JOYDUMPis not set
#CONFIG_JOYSTICK_XPADis not set
#CONFIG_INPUT_TABLETis not setCONFIG_INPUT_TOUCHSCREEN=y
#CONFIG_TOUCHSCREEN_AD7879is not set
#CONFIG_TOUCHSCREEN_DYNAPROis not set
#CONFIG_TOUCHSCREEN_HAMPSHIREis not set
#CONFIG_TOUCHSCREEN_EETIis not set
#CONFIG_TOUCHSCREEN_FUJITSUis not set
#CONFIG_TOUCHSCREEN_GUNZEis not set
#CONFIG_TOUCHSCREEN_ELOis not set
#CONFIG_TOUCHSCREEN_WACOM_W8001is not set
#CONFIG_TOUCHSCREEN_MCS5000is not set
#CONFIG_TOUCHSCREEN_MTOUCHis not set
#CONFIG_TOUCHSCREEN_INEXIOis not set
#CONFIG_TOUCHSCREEN_MK712is not set
#CONFIG_TOUCHSCREEN_PENMOUNTis not set
#CONFIG_TOUCHSCREEN_QT602240is not set
#CONFIG_TOUCHSCREEN_TOUCHRIGHTis not set
#CONFIG_TOUCHSCREEN_TOUCHWINis not set
#CONFIG_TOUCHSCREEN_WM97XXis not set
#CONFIG_TOUCHSCREEN_USB_COMPOSITEis not set
#CONFIG_TOUCHSCREEN_TOUCHIT213is not set
#CONFIG_TOUCHSCREEN_TSC2007is not set
#CONFIG_TOUCHSCREEN_TPS6507Xis not setCONFIG_INPUT_MISC=y
#CONFIG_INPUT_AD714Xis not set
#CONFIG_INPUT_PCSPKRis not set
#CONFIG_INPUT_ATLAS_BTNSis not set
#CONFIG_INPUT_ATI_REMOTEis not set
#CONFIG_INPUT_ATI_REMOTE2is not set
#CONFIG_INPUT_KEYSPAN_REMOTEis not set
#CONFIG_INPUT_POWERMATEis not set
#CONFIG_INPUT_YEALINKis not set
#CONFIG_INPUT_CM109is not set
#CONFIG_INPUT_UINPUTis not set
#CONFIG_INPUT_WINBOND_CIRis not set
#CONFIG_INPUT_PCF8574is not set
#CONFIG_INPUT_ADXL34Xis not set#
# Hardware I/O ports
#CONFIG_SERIO=yCONFIG_SERIO_I8042=yCONFIG_SERIO_SERPORT=y
#CONFIG_SERIO_CT82C710is not set
#CONFIG_SERIO_PCIPS2is not setCONFIG_SERIO_LIBPS2=y
#CONFIG_SERIO_RAWis not set
#CONFIG_SERIO_ALTERA_PS2is not set
#CONFIG_GAMEPORTis not set#
# Character devices
#CONFIG_VT=yCONFIG_CONSOLE_TRANSLATIONS=yCONFIG_VT_CONSOLE=yCONFIG_HW_CONSOLE=y
#CONFIG_VT_HW_CONSOLE_BINDINGis not setCONFIG_DEVKMEM=yCONFIG_SERIAL_NONSTANDARD=y
#CONFIG_COMPUTONEis not set
#CONFIG_ROCKETPORTis not set
#CONFIG_CYCLADESis not set
#CONFIG_DIGIEPCAis not set
#CONFIG_MOXA_INTELLIOis not set
#CONFIG_MOXA_SMARTIOis not set
#CONFIG_ISIis not set
#CONFIG_SYNCLINKis not set
#CONFIG_SYNCLINKMPis not set
#CONFIG_SYNCLINK_GTis not set
#CONFIG_N_HDLCis not set
#CONFIG_N_GSMis not set
#CONFIG_RISCOM8is not set
#CONFIG_SPECIALIXis not setCONFIG_STALDRV=y
#CONFIG_STALLIONis not set
#CONFIG_ISTALLIONis not set
#CONFIG_NOZOMIis not set#
# Serial drivers
#CONFIG_SERIAL_8250=yCONFIG_SERIAL_8250_CONSOLE=yCONFIG_FIX_EARLYCON_MEM=yCONFIG_SERIAL_8250_PCI=yCONFIG_SERIAL_8250_PNP=yCONFIG_SERIAL_8250_NR_UARTS=32CONFIG_SERIAL_8250_RUNTIME_UARTS=4CONFIG_SERIAL_8250_EXTENDED=yCONFIG_SERIAL_8250_MANY_PORTS=yCONFIG_SERIAL_8250_SHARE_IRQ=yCONFIG_SERIAL_8250_DETECT_IRQ=yCONFIG_SERIAL_8250_RSA=y#
# Non-8250 serial port support
#
#CONFIG_SERIAL_MFD_HSUis not setCONFIG_SERIAL_CORE=yCONFIG_SERIAL_CORE_CONSOLE=y
#CONFIG_SERIAL_JSMis not set
#CONFIG_SERIAL_TIMBERDALEis not set
#CONFIG_SERIAL_ALTERA_JTAGUARTis not set
#CONFIG_SERIAL_ALTERA_UARTis not setCONFIG_UNIX98_PTYS=y
#CONFIG_DEVPTS_MULTIPLE_INSTANCESis not set
#CONFIG_LEGACY_PTYSis not set
#CONFIG_IPMI_HANDLERis not set
#CONFIG_HW_RANDOMis not set
#CONFIG_NVRAMis not setCONFIG_RTC=y
#CONFIG_R3964is not set
#CONFIG_APPLICOMis not set
#CONFIG_MWAVEis not set
#CONFIG_RAW_DRIVERis not setCONFIG_HPET=y
#CONFIG_HPET_MMAPis not set
#CONFIG_HANGCHECK_TIMERis not set
#CONFIG_TCG_TPMis not set
#CONFIG_TELCLOCKis not setCONFIG_DEVPORT=y
#CONFIG_RAMOOPSis not setCONFIG_I2C=yCONFIG_I2C_BOARDINFO=yCONFIG_I2C_COMPAT=y
#CONFIG_I2C_CHARDEVis not set
#CONFIG_I2C_MUXis not setCONFIG_I2C_HELPER_AUTO=yCONFIG_I2C_ALGOBIT=y#
# I2C Hardware Bus support
##
# PC SMBus host controller drivers
#
#CONFIG_I2C_ALI1535is not set
#CONFIG_I2C_ALI1563is not set
#CONFIG_I2C_ALI15X3is not set
#CONFIG_I2C_AMD756is not set
#CONFIG_I2C_AMD8111is not set
#CONFIG_I2C_I801is not set
#CONFIG_I2C_ISCHis not set
#CONFIG_I2C_PIIX4is not set
#CONFIG_I2C_NFORCE2is not set
#CONFIG_I2C_SIS5595is not set
#CONFIG_I2C_SIS630is not set
#CONFIG_I2C_SIS96Xis not set
#CONFIG_I2C_VIAis not set
#CONFIG_I2C_VIAPROis not set#
# ACPI drivers
#
#CONFIG_I2C_SCMIis not set#
# I2C system bus drivers (mostly embedded / system-on-chip) #
#CONFIG_I2C_OCORESis not set
#CONFIG_I2C_PCA_PLATFORMis not set
#CONFIG_I2C_SIMTECis not set
#CONFIG_I2C_XILINXis not set#
# External I2C/SMBus adapter drivers
#
#CONFIG_I2C_PARPORT_LIGHTis not set
#CONFIG_I2C_TAOS_EVMis not set
#CONFIG_I2C_TINY_USBis not set#
# Other I2C/SMBus bus drivers
#
#CONFIG_I2C_DEBUG_COREis not set
#CONFIG_I2C_DEBUG_ALGOis not set
#CONFIG_I2C_DEBUG_BUSis not set
#CONFIG_SPIis not set#
# PPS support
#
#CONFIG_PPSis not setCONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
#CONFIG_GPIOLIBis not set
#CONFIG_W1is not setCONFIG_POWER_SUPPLY=y
#CONFIG_POWER_SUPPLY_DEBUGis not set
#CONFIG_PDA_POWERis not set
#CONFIG_TEST_POWERis not set
#CONFIG_BATTERY_DS2760is not set
#CONFIG_BATTERY_DS2782is not set
#CONFIG_BATTERY_BQ27x00is not set
#CONFIG_BATTERY_MAX17040is not setCONFIG_HWMON=y
#CONFIG_HWMON_VIDis not set
#CONFIG_HWMON_DEBUG_CHIPis not set#
# Native drivers
#
#CONFIG_SENSORS_ABITUGURUis not set
#CONFIG_SENSORS_ABITUGURU3is not set
#CONFIG_SENSORS_AD7414is not set
#CONFIG_SENSORS_AD7418is not set
#CONFIG_SENSORS_ADM1021is not set
#CONFIG_SENSORS_ADM1025is not set
#CONFIG_SENSORS_ADM1026is not set
#CONFIG_SENSORS_ADM1029is not set
#CONFIG_SENSORS_ADM1031is not set
#CONFIG_SENSORS_ADM9240is not set
#CONFIG_SENSORS_ADT7411is not set
#CONFIG_SENSORS_ADT7462is not set
#CONFIG_SENSORS_ADT7470is not set
#CONFIG_SENSORS_ADT7475is not set
#CONFIG_SENSORS_ASC7621is not set
#CONFIG_SENSORS_K8TEMPis not set
#CONFIG_SENSORS_K10TEMPis not set
#CONFIG_SENSORS_ASB100is not set
#CONFIG_SENSORS_ATXP1is not set
#CONFIG_SENSORS_DS1621is not set
#CONFIG_SENSORS_I5K_AMBis not set
#CONFIG_SENSORS_F71805Fis not set
#CONFIG_SENSORS_F71882FGis not set
#CONFIG_SENSORS_F75375Sis not set
#CONFIG_SENSORS_FSCHMDis not set
#CONFIG_SENSORS_G760Ais not set
#CONFIG_SENSORS_GL518SMis not set
#CONFIG_SENSORS_GL520SMis not set
#CONFIG_SENSORS_CORETEMPis not set
#CONFIG_SENSORS_PKGTEMPis not set
#CONFIG_SENSORS_IT87is not set
#CONFIG_SENSORS_JC42is not set
#CONFIG_SENSORS_LM63is not set
#CONFIG_SENSORS_LM73is not set
#CONFIG_SENSORS_LM75is not set
#CONFIG_SENSORS_LM77is not set
#CONFIG_SENSORS_LM78is not set
#CONFIG_SENSORS_LM80is not set
#CONFIG_SENSORS_LM83is not set
#CONFIG_SENSORS_LM85is not set
#CONFIG_SENSORS_LM87is not set
#CONFIG_SENSORS_LM90is not set
#CONFIG_SENSORS_LM92is not set
#CONFIG_SENSORS_LM93is not set
#CONFIG_SENSORS_LTC4215is not set
#CONFIG_SENSORS_LTC4245is not set
#CONFIG_SENSORS_LM95241is not set
#CONFIG_SENSORS_MAX1619is not set
#CONFIG_SENSORS_MAX6650is not set
#CONFIG_SENSORS_PC87360is not set
#CONFIG_SENSORS_PC87427is not set
#CONFIG_SENSORS_PCF8591is not set
#CONFIG_SENSORS_SIS5595is not set
#CONFIG_SENSORS_SMM665is not set
#CONFIG_SENSORS_DME1737is not set
#CONFIG_SENSORS_EMC1403is not set
#CONFIG_SENSORS_EMC2103is not set
#CONFIG_SENSORS_SMSC47M1is not set
#CONFIG_SENSORS_SMSC47M192is not set
#CONFIG_SENSORS_SMSC47B397is not set
#CONFIG_SENSORS_ADS7828is not set
#CONFIG_SENSORS_AMC6821is not set
#CONFIG_SENSORS_THMC50is not set
#CONFIG_SENSORS_TMP102is not set
#CONFIG_SENSORS_TMP401is not set
#CONFIG_SENSORS_TMP421is not set
#CONFIG_SENSORS_VIA_CPUTEMPis not set
#CONFIG_SENSORS_VIA686Ais not set
#CONFIG_SENSORS_VT1211is not set
#CONFIG_SENSORS_VT8231is not set
#CONFIG_SENSORS_W83781Dis not set
#CONFIG_SENSORS_W83791Dis not set
#CONFIG_SENSORS_W83792Dis not set
#CONFIG_SENSORS_W83793is not set
#CONFIG_SENSORS_W83L785TSis not set
#CONFIG_SENSORS_W83L786NGis not set
#CONFIG_SENSORS_W83627HFis not set
#CONFIG_SENSORS_W83627EHFis not set
#CONFIG_SENSORS_HDAPSis not set
#CONFIG_SENSORS_LIS3_I2Cis not set
#CONFIG_SENSORS_APPLESMCis not set#
# ACPI drivers
#
#CONFIG_SENSORS_ATK0110is not set
#CONFIG_SENSORS_LIS3LV02Dis not setCONFIG_THERMAL=y
#CONFIG_THERMAL_HWMONis not setCONFIG_WATCHDOG=y
#CONFIG_WATCHDOG_NOWAYOUTis not set#
# Watchdog Device Drivers
#
#CONFIG_SOFT_WATCHDOGis not set
#CONFIG_ACQUIRE_WDTis not set
#CONFIG_ADVANTECH_WDTis not set
#CONFIG_ALIM1535_WDTis not set
#CONFIG_ALIM7101_WDTis not set
#CONFIG_F71808E_WDTis not set
#CONFIG_SC520_WDTis not set
#CONFIG_SBC_FITPC2_WATCHDOGis not set
#CONFIG_EUROTECH_WDTis not set
#CONFIG_IB700_WDTis not set
#CONFIG_IBMASRis not set
#CONFIG_WAFER_WDTis not set
#CONFIG_I6300ESB_WDTis not set
#CONFIG_ITCO_WDTis not set
#CONFIG_IT8712F_WDTis not set
#CONFIG_IT87_WDTis not set
#CONFIG_HP_WATCHDOGis not set
#CONFIG_SC1200_WDTis not set
#CONFIG_PC87413_WDTis not set
#CONFIG_60XX_WDTis not set
#CONFIG_SBC8360_WDTis not set
#CONFIG_CPU5_WDTis not set
#CONFIG_SMSC_SCH311X_WDTis not set
#CONFIG_SMSC37B787_WDTis not set
#CONFIG_W83627HF_WDTis not set
#CONFIG_W83697HF_WDTis not set
#CONFIG_W83697UG_WDTis not set
#CONFIG_W83877F_WDTis not set
#CONFIG_W83977F_WDTis not set
#CONFIG_MACHZ_WDTis not set
#CONFIG_SBC_EPX_C3_WATCHDOGis not set#
# PCI-based Watchdog Cards
#
#CONFIG_PCIPCWATCHDOGis not set
#CONFIG_WDTPCIis not set#
# USB-based Watchdog Cards
#
#CONFIG_USBPCWATCHDOGis not setCONFIG_SSB_POSSIBLE=y#
# Sonics Silicon Backplane
#
#CONFIG_SSBis not setCONFIG_MFD_SUPPORT=y
#CONFIG_MFD_COREis not set
#CONFIG_MFD_88PM860Xis not set
#CONFIG_MFD_SM501is not set
#CONFIG_HTC_PASIC3is not set
#CONFIG_TPS6507Xis not set
#CONFIG_TWL4030_COREis not set
#CONFIG_MFD_STMPEis not set
#CONFIG_MFD_TC35892is not set
#CONFIG_MFD_TMIOis not set
#CONFIG_PMIC_DA903Xis not set
#CONFIG_PMIC_ADP5520is not set
#CONFIG_MFD_MAX8925is not set
#CONFIG_MFD_MAX8998is not set
#CONFIG_MFD_WM8400is not set
#CONFIG_MFD_WM831Xis not set
#CONFIG_MFD_WM8350_I2Cis not set
#CONFIG_MFD_WM8994is not set
#CONFIG_MFD_PCF50633is not set
#CONFIG_ABX500_COREis not set
#CONFIG_LPC_SCHis not set
#CONFIG_MFD_RDC321Xis not set
#CONFIG_MFD_JANZ_CMODIOis not set
#CONFIG_REGULATORis not set
#CONFIG_MEDIA_SUPPORTis not set#
# Graphics support
#CONFIG_AGP=yCONFIG_AGP_AMD64=yCONFIG_AGP_INTEL=y
#CONFIG_AGP_SISis not set
#CONFIG_AGP_VIAis not setCONFIG_VGA_ARB=yCONFIG_VGA_ARB_MAX_GPUS=16
#CONFIG_VGA_SWITCHEROOis not setCONFIG_DRM=yCONFIG_DRM_KMS_HELPER=y
#CONFIG_DRM_TDFXis not set
#CONFIG_DRM_R128is not set
#CONFIG_DRM_RADEONis not set
#CONFIG_DRM_I810is not set
#CONFIG_DRM_I830is not setCONFIG_DRM_I915=y
#CONFIG_DRM_I915_KMSis not set
#CONFIG_DRM_MGAis not set
#CONFIG_DRM_SISis not set
#CONFIG_DRM_VIAis not set
#CONFIG_DRM_SAVAGEis not set
#CONFIG_VGASTATEis not setCONFIG_VIDEO_OUTPUT_CONTROL=yCONFIG_FB=yCONFIG_FIRMWARE_EDID=y
#CONFIG_FB_DDCis not setCONFIG_FB_BOOT_VESA_SUPPORT=yCONFIG_FB_CFB_FILLRECT=yCONFIG_FB_CFB_COPYAREA=yCONFIG_FB_CFB_IMAGEBLIT=y
#CONFIG_FB_CFB_REV_PIXELS_IN_BYTEis not set
#CONFIG_FB_SYS_FILLRECTis not set
#CONFIG_FB_SYS_COPYAREAis not set
#CONFIG_FB_SYS_IMAGEBLITis not set
#CONFIG_FB_FOREIGN_ENDIANis not set
#CONFIG_FB_SYS_FOPSis not set
#CONFIG_FB_SVGALIBis not set
#CONFIG_FB_MACMODESis not set
#CONFIG_FB_BACKLIGHTis not setCONFIG_FB_MODE_HELPERS=yCONFIG_FB_TILEBLITTING=y#
# Frame buffer hardware drivers
#
#CONFIG_FB_CIRRUSis not set
#CONFIG_FB_PM2is not set
#CONFIG_FB_CYBER2000is not set
#CONFIG_FB_ARCis not set
#CONFIG_FB_ASILIANTis not set
#CONFIG_FB_IMSTTis not set
#CONFIG_FB_VGA16is not setCONFIG_FB_VESA=y
#CONFIG_FB_N411is not set
#CONFIG_FB_HGAis not set
#CONFIG_FB_S1D13XXXis not set
#CONFIG_FB_NVIDIAis not set
#CONFIG_FB_RIVAis not set
#CONFIG_FB_LE80578is not set
#CONFIG_FB_MATROXis not set
#CONFIG_FB_RADEONis not set
#CONFIG_FB_ATY128is not set
#CONFIG_FB_ATYis not set
#CONFIG_FB_S3is not set
#CONFIG_FB_SAVAGEis not set
#CONFIG_FB_SISis not set
#CONFIG_FB_VIAis not set
#CONFIG_FB_NEOMAGICis not set
#CONFIG_FB_KYROis not set
#CONFIG_FB_3DFXis not set
#CONFIG_FB_VOODOO1is not set
#CONFIG_FB_VT8623is not set
#CONFIG_FB_TRIDENTis not set
#CONFIG_FB_ARKis not set
#CONFIG_FB_PM3is not set
#CONFIG_FB_CARMINEis not set
#CONFIG_FB_GEODEis not set
#CONFIG_FB_VIRTUALis not set
#CONFIG_FB_METRONOMEis not set
#CONFIG_FB_MB862XXis not set
#CONFIG_FB_BROADSHEETis not setCONFIG_BACKLIGHT_LCD_SUPPORT=y
#CONFIG_LCD_CLASS_DEVICEis not setCONFIG_BACKLIGHT_CLASS_DEVICE=yCONFIG_BACKLIGHT_GENERIC=y
#CONFIG_BACKLIGHT_PROGEARis not set
#CONFIG_BACKLIGHT_MBP_NVIDIAis not set
#CONFIG_BACKLIGHT_SAHARAis not set
#CONFIG_BACKLIGHT_ADP8860is not set#
# Display device support
#CONFIG_DISPLAY_SUPPORT=y#
# Display hardware drivers
##
# Console display driver support
#CONFIG_VGA_CONSOLE=y
#CONFIG_VGACON_SOFT_SCROLLBACKis not setCONFIG_DUMMY_CONSOLE=yCONFIG_FRAMEBUFFER_CONSOLE=y
#CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARYis not set #CONFIG_FRAMEBUFFER_CONSOLE_ROTATIONis not set #CONFIG_FONTSis not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=yCONFIG_LOGO=y
#CONFIG_LOGO_LINUX_MONOis not set
#CONFIG_LOGO_LINUX_VGA16is not setCONFIG_LOGO_LINUX_CLUT224=yCONFIG_SOUND=yCONFIG_SOUND_OSS_CORE=yCONFIG_SOUND_OSS_CORE_PRECLAIM=yCONFIG_SND=yCONFIG_SND_TIMER=yCONFIG_SND_PCM=yCONFIG_SND_SEQUENCER=y
#CONFIG_SND_SEQ_DUMMYis not setCONFIG_SND_OSSEMUL=yCONFIG_SND_MIXER_OSS=yCONFIG_SND_PCM_OSS=yCONFIG_SND_PCM_OSS_PLUGINS=yCONFIG_SND_SEQUENCER_OSS=yCONFIG_SND_HRTIMER=yCONFIG_SND_SEQ_HRTIMER_DEFAULT=yCONFIG_SND_RTCTIMER=yCONFIG_SND_DYNAMIC_MINORS=yCONFIG_SND_SUPPORT_OLD_API=y
#CONFIG_SND_VERBOSE_PROCFSis not set
#CONFIG_SND_VERBOSE_PRINTKis not set
#CONFIG_SND_DEBUGis not setCONFIG_SND_VMASTER=yCONFIG_SND_DMA_SGBUF=y
#CONFIG_SND_RAWMIDI_SEQis not set
#CONFIG_SND_OPL3_LIB_SEQis not set
#CONFIG_SND_OPL4_LIB_SEQis not set
#CONFIG_SND_SBAWE_SEQis not set
#CONFIG_SND_EMU10K1_SEQis not setCONFIG_SND_AC97_CODEC=yCONFIG_SND_DRIVERS=y
#CONFIG_SND_PCSPis not set
#CONFIG_SND_DUMMYis not set
#CONFIG_SND_VIRMIDIis not set
#CONFIG_SND_MTPAVis not set
#CONFIG_SND_SERIAL_U16550is not set
#CONFIG_SND_MPU401is not set
#CONFIG_SND_AC97_POWER_SAVEis not setCONFIG_SND_PCI=y
#CONFIG_SND_AD1889is not set
#CONFIG_SND_ALS300is not set
#CONFIG_SND_ALS4000is not set
#CONFIG_SND_ALI5451is not set
#CONFIG_SND_ASIHPIis not set
#CONFIG_SND_ATIIXPis not set
#CONFIG_SND_ATIIXP_MODEMis not set
#CONFIG_SND_AU8810is not set
#CONFIG_SND_AU8820is not set
#CONFIG_SND_AU8830is not set
#CONFIG_SND_AW2is not set
#CONFIG_SND_AZT3328is not set
#CONFIG_SND_BT87Xis not set
#CONFIG_SND_CA0106is not set
#CONFIG_SND_CMIPCIis not set
#CONFIG_SND_OXYGENis not set
#CONFIG_SND_CS4281is not set
#CONFIG_SND_CS46XXis not set
#CONFIG_SND_CS5530is not set
#CONFIG_SND_CS5535AUDIOis not set
#CONFIG_SND_CTXFIis not set
#CONFIG_SND_DARLA20is not set
#CONFIG_SND_GINA20is not set
#CONFIG_SND_LAYLA20is not set
#CONFIG_SND_DARLA24is not set
#CONFIG_SND_GINA24is not set
#CONFIG_SND_LAYLA24is not set
#CONFIG_SND_MONAis not set
#CONFIG_SND_MIAis not set
#CONFIG_SND_ECHO3Gis not set
#CONFIG_SND_INDIGOis not set
#CONFIG_SND_INDIGOIOis not set
#CONFIG_SND_INDIGODJis not set
#CONFIG_SND_INDIGOIOXis not set
#CONFIG_SND_INDIGODJXis not set
#CONFIG_SND_EMU10K1is not set
#CONFIG_SND_EMU10K1Xis not set
#CONFIG_SND_ENS1370is not set
#CONFIG_SND_ENS1371is not set
#CONFIG_SND_ES1938is not set
#CONFIG_SND_ES1968is not set
#CONFIG_SND_FM801is not setCONFIG_SND_HDA_INTEL=y
#CONFIG_SND_HDA_HWDEPis not setCONFIG_SND_HDA_INPUT_BEEP=yCONFIG_SND_HDA_INPUT_BEEP_MODE=1
#CONFIG_SND_HDA_INPUT_JACKis not set
#CONFIG_SND_HDA_PATCH_LOADERis not setCONFIG_SND_HDA_CODEC_REALTEK=yCONFIG_SND_HDA_CODEC_ANALOG=yCONFIG_SND_HDA_CODEC_SIGMATEL=yCONFIG_SND_HDA_CODEC_VIA=yCONFIG_SND_HDA_CODEC_ATIHDMI=y
#CONFIG_SND_HDA_CODEC_NVHDMIis not setCONFIG_SND_HDA_CODEC_INTELHDMI=yCONFIG_SND_HDA_ELD=yCONFIG_SND_HDA_CODEC_CIRRUS=yCONFIG_SND_HDA_CODEC_CONEXANT=yCONFIG_SND_HDA_CODEC_CA0110=yCONFIG_SND_HDA_CODEC_CMEDIA=yCONFIG_SND_HDA_CODEC_SI3054=yCONFIG_SND_HDA_GENERIC=y
#CONFIG_SND_HDA_POWER_SAVEis not set
#CONFIG_SND_HDSPis not set
#CONFIG_SND_HDSPMis not set
#CONFIG_SND_HIFIERis not set
#CONFIG_SND_ICE1712is not set
#CONFIG_SND_ICE1724is not setCONFIG_SND_INTEL8X0=y
#CONFIG_SND_INTEL8X0Mis not set
#CONFIG_SND_KORG1212is not set
#CONFIG_SND_LX6464ESis not set
#CONFIG_SND_MAESTRO3is not set
#CONFIG_SND_MIXARTis not set
#CONFIG_SND_NM256is not set
#CONFIG_SND_PCXHRis not set
#CONFIG_SND_RIPTIDEis not set
#CONFIG_SND_RME32is not set
#CONFIG_SND_RME96is not set
#CONFIG_SND_RME9652is not set
#CONFIG_SND_SONICVIBESis not set
#CONFIG_SND_TRIDENTis not set
#CONFIG_SND_VIA82XXis not set
#CONFIG_SND_VIA82XX_MODEMis not set
#CONFIG_SND_VIRTUOSOis not set
#CONFIG_SND_VX222is not set
#CONFIG_SND_YMFPCIis not setCONFIG_SND_USB=y
#CONFIG_SND_USB_AUDIOis not set
#CONFIG_SND_USB_UA101is not set
#CONFIG_SND_USB_USX2Yis not set
#CONFIG_SND_USB_CAIAQis not set
#CONFIG_SND_USB_US122Lis not set
#CONFIG_SND_SOCis not set
#CONFIG_SOUND_PRIMEis not setCONFIG_AC97_BUS=yCONFIG_HID_SUPPORT=yCONFIG_HID=y
#CONFIG_HIDRAWis not set#
# USB Input Devices
#CONFIG_USB_HID=yCONFIG_HID_PID=yCONFIG_USB_HIDDEV=y#
# Special HID drivers
#
#CONFIG_HID_3M_PCTis not setCONFIG_HID_A4TECH=y
#CONFIG_HID_ACRUX_FFis not setCONFIG_HID_APPLE=yCONFIG_HID_BELKIN=y
#CONFIG_HID_CANDOis not setCONFIG_HID_CHERRY=yCONFIG_HID_CHICONY=y
#CONFIG_HID_PRODIKEYSis not setCONFIG_HID_CYPRESS=yCONFIG_HID_DRAGONRISE=y
#CONFIG_DRAGONRISE_FFis not set
#CONFIG_HID_EGALAXis not setCONFIG_HID_EZKEY=yCONFIG_HID_KYE=yCONFIG_HID_GYRATION=yCONFIG_HID_TWINHAN=yCONFIG_HID_KENSINGTON=yCONFIG_HID_LOGITECH=yCONFIG_LOGITECH_FF=y
#CONFIG_LOGIRUMBLEPAD2_FFis not set
#CONFIG_LOGIG940_FFis not setCONFIG_HID_MICROSOFT=y
#CONFIG_HID_MOSARTis not setCONFIG_HID_MONTEREY=yCONFIG_HID_NTRIG=yCONFIG_HID_ORTEK=yCONFIG_HID_PANTHERLORD=y
#CONFIG_PANTHERLORD_FFis not setCONFIG_HID_PETALYNX=y
#CONFIG_HID_PICOLCDis not set
#CONFIG_HID_QUANTAis not set
#CONFIG_HID_ROCCATis not set
#CONFIG_HID_ROCCAT_KONEis not setCONFIG_HID_SAMSUNG=yCONFIG_HID_SONY=y
#CONFIG_HID_STANTUMis not setCONFIG_HID_SUNPLUS=yCONFIG_HID_GREENASIA=y
#CONFIG_GREENASIA_FFis not setCONFIG_HID_SMARTJOYPLUS=y
#CONFIG_SMARTJOYPLUS_FFis not setCONFIG_HID_TOPSEED=yCONFIG_HID_THRUSTMASTER=yCONFIG_THRUSTMASTER_FF=yCONFIG_HID_ZEROPLUS=y
#CONFIG_ZEROPLUS_FFis not set
#CONFIG_HID_ZYDACRONis not setCONFIG_USB_SUPPORT=yCONFIG_USB_ARCH_HAS_HCD=yCONFIG_USB_ARCH_HAS_OHCI=yCONFIG_USB_ARCH_HAS_EHCI=yCONFIG_USB=y
#CONFIG_USB_DEBUGis not setCONFIG_USB_ANNOUNCE_NEW_DEVICES=y#
# Miscellaneous USB options
#
#CONFIG_USB_DEVICEFSis not set
#CONFIG_USB_DEVICE_CLASSis not set
#CONFIG_USB_DYNAMIC_MINORSis not setCONFIG_USB_MON=y
#CONFIG_USB_WUSBis not set
#CONFIG_USB_WUSB_CBAFis not set#
# USB Host Controller Drivers
#
#CONFIG_USB_C67X00_HCDis not set
#CONFIG_USB_XHCI_HCDis not setCONFIG_USB_EHCI_HCD=yCONFIG_USB_EHCI_ROOT_HUB_TT=y
#CONFIG_USB_EHCI_TT_NEWSCHEDis not set
#CONFIG_USB_OXU210HP_HCDis not set
#CONFIG_USB_ISP116X_HCDis not set
#CONFIG_USB_ISP1760_HCDis not set
#CONFIG_USB_ISP1362_HCDis not set
#CONFIG_USB_OHCI_HCDis not setCONFIG_USB_UHCI_HCD=y
#CONFIG_USB_SL811_HCDis not set
#CONFIG_USB_R8A66597_HCDis not set
#CONFIG_USB_WHCI_HCDis not set
#CONFIG_USB_HWA_HCDis not set#
# USB Device Class drivers
#
#CONFIG_USB_ACMis not setCONFIG_USB_PRINTER=y
#CONFIG_USB_WDMis not set
#CONFIG_USB_TMCis not set#
# NOTE:USB_STORAGEdepends on SCSI butBLK_DEV_SDmay ##
# also be needed; see USB_STORAGE Help for more info # CONFIG_USB_STORAGE=y # CONFIG_USB_STORAGE_DEBUG is not set # CONFIG_USB_STORAGE_DATAFAB is not set # CONFIG_USB_STORAGE_FREECOM is not set # CONFIG_USB_STORAGE_ISD200 is not set # CONFIG_USB_STORAGE_USBAT is not set # CONFIG_USB_STORAGE_SDDR09 is not set # CONFIG_USB_STORAGE_SDDR55 is not set # CONFIG_USB_STORAGE_JUMPSHOT is not set # CONFIG_USB_STORAGE_ALAUDA is not set # CONFIG_USB_STORAGE_ONETOUCH is not set # CONFIG_USB_STORAGE_KARMA is not set # CONFIG_USB_STORAGE_CYPRESS_ATACB is not set # CONFIG_USB_LIBUSUAL is not set#
# USB Imaging devices
#
#CONFIG_USB_MDC800is not set
#CONFIG_USB_MICROTEKis not set#
# USB port drivers
#
#CONFIG_USB_SERIALis not set#
# USB Miscellaneous drivers
#
#CONFIG_USB_EMI62is not set
#CONFIG_USB_EMI26is not set
#CONFIG_USB_ADUTUXis not set
#CONFIG_USB_SEVSEGis not set
#CONFIG_USB_RIO500is not set
#CONFIG_USB_LEGOTOWERis not set
#CONFIG_USB_LCDis not set
#CONFIG_USB_LEDis not set
#CONFIG_USB_CYPRESS_CY7C63is not set
#CONFIG_USB_CYTHERMis not set
#CONFIG_USB_IDMOUSEis not set
#CONFIG_USB_FTDI_ELANis not set
#CONFIG_USB_APPLEDISPLAYis not set
#CONFIG_USB_SISUSBVGAis not set
#CONFIG_USB_LDis not set
#CONFIG_USB_TRANCEVIBRATORis not set
#CONFIG_USB_IOWARRIORis not set
#CONFIG_USB_TESTis not set
#CONFIG_USB_ISIGHTFWis not set
#CONFIG_USB_GADGETis not set#
# OTG and related infrastructure
#
#CONFIG_NOP_USB_XCEIVis not set
#CONFIG_UWBis not set
#CONFIG_MMCis not set
#CONFIG_MEMSTICKis not set
#CONFIG_NEW_LEDSis not set
#CONFIG_ACCESSIBILITYis not set
#CONFIG_INFINIBANDis not setCONFIG_EDAC=y#
# Reporting subsystems
#
#CONFIG_EDAC_DEBUGis not setCONFIG_EDAC_DECODE_MCE=yCONFIG_EDAC_MM_EDAC=y
#CONFIG_EDAC_AMD64is not set
#CONFIG_EDAC_E752Xis not set
#CONFIG_EDAC_I82975Xis not set
#CONFIG_EDAC_I3000is not set
#CONFIG_EDAC_I3200is not set
#CONFIG_EDAC_X38is not set
#CONFIG_EDAC_I5400is not set
#CONFIG_EDAC_I7COREis not set
#CONFIG_EDAC_I5000is not set
#CONFIG_EDAC_I5100is not set
#CONFIG_RTC_CLASSis not set
#CONFIG_DMADEVICESis not set
#CONFIG_AUXDISPLAYis not set
#CONFIG_UIOis not set
#CONFIG_STAGINGis not setCONFIG_X86_PLATFORM_DEVICES=y
#CONFIG_ASUS_LAPTOPis not set
#CONFIG_DELL_WMIis not set
#CONFIG_FUJITSU_LAPTOPis not set
#CONFIG_HP_WMIis not set
#CONFIG_PANASONIC_LAPTOPis not set
#CONFIG_THINKPAD_ACPIis not set
#CONFIG_INTEL_MENLOWis not set
#CONFIG_EEEPC_LAPTOPis not set
#CONFIG_EEEPC_WMIis not setCONFIG_ACPI_WMI=y
#CONFIG_MSI_WMIis not set
#CONFIG_ACPI_ASUSis not set
#CONFIG_TOPSTAR_LAPTOPis not set
#CONFIG_TOSHIBA_BT_RFKILLis not set
#CONFIG_ACPI_CMPCis not set
#CONFIG_INTEL_IPSis not set#
# Firmware Drivers
#
#CONFIG_EDDis not setCONFIG_FIRMWARE_MEMMAP=y
#CONFIG_DELL_RBUis not set
#CONFIG_DCDBASis not setCONFIG_DMIID=y
#CONFIG_ISCSI_IBFT_FINDis not set#
# File systems
#CONFIG_EXT2_FS=yCONFIG_EXT2_FS_XATTR=yCONFIG_EXT2_FS_POSIX_ACL=yCONFIG_EXT2_FS_SECURITY=y
#CONFIG_EXT2_FS_XIPis not setCONFIG_EXT3_FS=y
#CONFIG_EXT3_DEFAULTS_TO_ORDEREDis not setCONFIG_EXT3_FS_XATTR=yCONFIG_EXT3_FS_POSIX_ACL=y
#CONFIG_EXT3_FS_SECURITYis not set
#CONFIG_EXT4_FSis not setCONFIG_JBD=y
#CONFIG_JBD_DEBUGis not setCONFIG_FS_MBCACHE=y
#CONFIG_REISERFS_FSis not set
#CONFIG_JFS_FSis not setCONFIG_FS_POSIX_ACL=y
#CONFIG_XFS_FSis not set
#CONFIG_GFS2_FSis not set
#CONFIG_OCFS2_FSis not setCONFIG_BTRFS_FS=yCONFIG_BTRFS_FS_POSIX_ACL=y
#CONFIG_NILFS2_FSis not setCONFIG_FILE_LOCKING=yCONFIG_FSNOTIFY=yCONFIG_DNOTIFY=yCONFIG_INOTIFY_USER=y
#CONFIG_FANOTIFYis not set
#CONFIG_QUOTAis not set
#CONFIG_AUTOFS_FSis not setCONFIG_AUTOFS4_FS=y
#CONFIG_FUSE_FSis not setCONFIG_GENERIC_ACL=y#
# Caches
#
#CONFIG_FSCACHEis not set#
# CD-ROM/DVD Filesystems
#CONFIG_ISO9660_FS=yCONFIG_JOLIET=yCONFIG_ZISOFS=y
#CONFIG_UDF_FSis not set#
# DOS/FAT/NT Filesystems
#CONFIG_FAT_FS=yCONFIG_MSDOS_FS=yCONFIG_VFAT_FS=yCONFIG_FAT_DEFAULT_CODEPAGE=437CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
#CONFIG_NTFS_FSis not set#
# Pseudo filesystems
#CONFIG_PROC_FS=yCONFIG_PROC_KCORE=yCONFIG_PROC_SYSCTL=yCONFIG_PROC_PAGE_MONITOR=yCONFIG_SYSFS=yCONFIG_TMPFS=yCONFIG_TMPFS_POSIX_ACL=yCONFIG_HUGETLBFS=yCONFIG_HUGETLB_PAGE=y
#CONFIG_CONFIGFS_FSis not set
#CONFIG_MISC_FILESYSTEMSis not setCONFIG_NETWORK_FILESYSTEMS=y
#CONFIG_NFS_FSis not set
#CONFIG_NFSDis not set
#CONFIG_SMB_FSis not set
#CONFIG_CEPH_FSis not set
#CONFIG_CIFSis not set
#CONFIG_NCP_FSis not set
#CONFIG_CODA_FSis not set
#CONFIG_AFS_FSis not set#
# Partition Types
#CONFIG_PARTITION_ADVANCED=y
#CONFIG_ACORN_PARTITIONis not setCONFIG_OSF_PARTITION=yCONFIG_AMIGA_PARTITION=y
#CONFIG_ATARI_PARTITIONis not setCONFIG_MAC_PARTITION=yCONFIG_MSDOS_PARTITION=yCONFIG_BSD_DISKLABEL=yCONFIG_MINIX_SUBPARTITION=yCONFIG_SOLARIS_X86_PARTITION=yCONFIG_UNIXWARE_DISKLABEL=y
#CONFIG_LDM_PARTITIONis not setCONFIG_SGI_PARTITION=y
#CONFIG_ULTRIX_PARTITIONis not setCONFIG_SUN_PARTITION=y
#CONFIG_KARMA_PARTITIONis not setCONFIG_EFI_PARTITION=y
#CONFIG_SYSV68_PARTITIONis not setCONFIG_NLS=yCONFIG_NLS_DEFAULT="utf8"CONFIG_NLS_CODEPAGE_437=y
#CONFIG_NLS_CODEPAGE_737is not set
#CONFIG_NLS_CODEPAGE_775is not set
#CONFIG_NLS_CODEPAGE_850is not set
#CONFIG_NLS_CODEPAGE_852is not set
#CONFIG_NLS_CODEPAGE_855is not set
#CONFIG_NLS_CODEPAGE_857is not set
#CONFIG_NLS_CODEPAGE_860is not set
#CONFIG_NLS_CODEPAGE_861is not set
#CONFIG_NLS_CODEPAGE_862is not set
#CONFIG_NLS_CODEPAGE_863is not set
#CONFIG_NLS_CODEPAGE_864is not set
#CONFIG_NLS_CODEPAGE_865is not set
#CONFIG_NLS_CODEPAGE_866is not set
#CONFIG_NLS_CODEPAGE_869is not set
#CONFIG_NLS_CODEPAGE_936is not set
#CONFIG_NLS_CODEPAGE_950is not set
#CONFIG_NLS_CODEPAGE_932is not set
#CONFIG_NLS_CODEPAGE_949is not set
#CONFIG_NLS_CODEPAGE_874is not set
#CONFIG_NLS_ISO8859_8is not set
#CONFIG_NLS_CODEPAGE_1250is not set
#CONFIG_NLS_CODEPAGE_1251is not setCONFIG_NLS_ASCII=yCONFIG_NLS_ISO8859_1=y
#CONFIG_NLS_ISO8859_2is not set
#CONFIG_NLS_ISO8859_3is not set
#CONFIG_NLS_ISO8859_4is not set
#CONFIG_NLS_ISO8859_5is not set
#CONFIG_NLS_ISO8859_6is not set
#CONFIG_NLS_ISO8859_7is not set
#CONFIG_NLS_ISO8859_9is not set
#CONFIG_NLS_ISO8859_13is not set
#CONFIG_NLS_ISO8859_14is not set
#CONFIG_NLS_ISO8859_15is not set
#CONFIG_NLS_KOI8_Ris not set
#CONFIG_NLS_KOI8_Uis not setCONFIG_NLS_UTF8=y
#CONFIG_DLMis not set#
# Kernel hacking
#CONFIG_TRACE_IRQFLAGS_SUPPORT=yCONFIG_PRINTK_TIME=y
#CONFIG_ENABLE_WARN_DEPRECATEDis not set
#CONFIG_ENABLE_MUST_CHECKis not setCONFIG_FRAME_WARN=2048CONFIG_MAGIC_SYSRQ=y
#CONFIG_STRIP_ASM_SYMSis not setCONFIG_UNUSED_SYMBOLS=yCONFIG_DEBUG_FS=y
#CONFIG_HEADERS_CHECKis not setCONFIG_DEBUG_KERNEL=y
#CONFIG_DEBUG_SHIRQis not set
#CONFIG_LOCKUP_DETECTORis not set
#CONFIG_HARDLOCKUP_DETECTORis not set
#CONFIG_DETECT_HUNG_TASKis not setCONFIG_SCHED_DEBUG=y
#CONFIG_SCHEDSTATSis not set
#CONFIG_TIMER_STATSis not set
#CONFIG_DEBUG_OBJECTSis not set
#CONFIG_SLUB_DEBUG_ONis not set
#CONFIG_SLUB_STATSis not set
#CONFIG_DEBUG_KMEMLEAKis not set
#CONFIG_DEBUG_RT_MUTEXESis not set
#CONFIG_RT_MUTEX_TESTERis not set
#CONFIG_DEBUG_SPINLOCKis not set
#CONFIG_DEBUG_MUTEXESis not set
#CONFIG_DEBUG_LOCK_ALLOCis not set
#CONFIG_PROVE_LOCKINGis not set
#CONFIG_LOCK_STATis not set
#CONFIG_DEBUG_SPINLOCK_SLEEPis not set
#CONFIG_DEBUG_LOCKING_API_SELFTESTSis not setCONFIG_STACKTRACE=y
#CONFIG_DEBUG_KOBJECTis not setCONFIG_DEBUG_BUGVERBOSE=y
#CONFIG_DEBUG_INFOis not set
#CONFIG_DEBUG_VMis not set
#CONFIG_DEBUG_VIRTUALis not set
#CONFIG_DEBUG_WRITECOUNTis not setCONFIG_DEBUG_MEMORY_INIT=y
#CONFIG_DEBUG_LISTis not set
#CONFIG_DEBUG_SGis not set
#CONFIG_DEBUG_NOTIFIERSis not set
#CONFIG_DEBUG_CREDENTIALSis not setCONFIG_ARCH_WANT_FRAME_POINTERS=yCONFIG_FRAME_POINTER=y
#CONFIG_BOOT_PRINTK_DELAYis not set
#CONFIG_RCU_TORTURE_TESTis not set
#CONFIG_RCU_CPU_STALL_DETECTORis not set
#CONFIG_BACKTRACE_SELF_TESTis not set
#CONFIG_DEBUG_BLOCK_EXT_DEVTis not set
#CONFIG_DEBUG_FORCE_WEAK_PER_CPUis not set
#CONFIG_LKDTMis not set
#CONFIG_FAULT_INJECTIONis not set
#CONFIG_LATENCYTOPis not setCONFIG_SYSCTL_SYSCALL_CHECK=y
#CONFIG_DEBUG_PAGEALLOCis not setCONFIG_USER_STACKTRACE_SUPPORT=yCONFIG_NOP_TRACER=yCONFIG_HAVE_FUNCTION_TRACER=yCONFIG_HAVE_FUNCTION_GRAPH_TRACER=yCONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=yCONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=yCONFIG_HAVE_DYNAMIC_FTRACE=yCONFIG_HAVE_FTRACE_MCOUNT_RECORD=yCONFIG_HAVE_SYSCALL_TRACEPOINTS=yCONFIG_RING_BUFFER=yCONFIG_EVENT_TRACING=yCONFIG_CONTEXT_SWITCH_TRACER=yCONFIG_RING_BUFFER_ALLOW_SWAP=yCONFIG_TRACING=yCONFIG_GENERIC_TRACER=yCONFIG_TRACING_SUPPORT=yCONFIG_FTRACE=y
#CONFIG_FUNCTION_TRACERis not set
#CONFIG_IRQSOFF_TRACERis not set
#CONFIG_SCHED_TRACERis not set
#CONFIG_FTRACE_SYSCALLSis not setCONFIG_BRANCH_PROFILE_NONE=y
#CONFIG_PROFILE_ANNOTATED_BRANCHESis not set
#CONFIG_PROFILE_ALL_BRANCHESis not set
#CONFIG_STACK_TRACERis not setCONFIG_BLK_DEV_IO_TRACE=y
#CONFIG_FTRACE_STARTUP_TESTis not set
#CONFIG_MMIOTRACEis not set
#CONFIG_RING_BUFFER_BENCHMARKis not set
#CONFIG_PROVIDE_OHCI1394_DMA_INITis not set
#CONFIG_DYNAMIC_DEBUGis not set
#CONFIG_DMA_API_DEBUGis not set
#CONFIG_ATOMIC64_SELFTESTis not set
#CONFIG_SAMPLESis not setCONFIG_HAVE_ARCH_KGDB=y
#CONFIG_KGDBis not setCONFIG_HAVE_ARCH_KMEMCHECK=yCONFIG_STRICT_DEVMEM=y
#CONFIG_X86_VERBOSE_BOOTUPis not setCONFIG_EARLY_PRINTK=y
#CONFIG_EARLY_PRINTK_DBGPis not set
#CONFIG_DEBUG_STACKOVERFLOWis not set
#CONFIG_DEBUG_STACK_USAGEis not set
#CONFIG_X86_PTDUMPis not setCONFIG_DEBUG_RODATA=y
#CONFIG_DEBUG_RODATA_TESTis not set
#CONFIG_IOMMU_DEBUGis not set
#CONFIG_IOMMU_STRESSis not setCONFIG_HAVE_MMIOTRACE_SUPPORT=yCONFIG_IO_DELAY_TYPE_0X80=0CONFIG_IO_DELAY_TYPE_0XED=1CONFIG_IO_DELAY_TYPE_UDELAY=2CONFIG_IO_DELAY_TYPE_NONE=3CONFIG_IO_DELAY_0X80=y
#CONFIG_IO_DELAY_0XEDis not set
#CONFIG_IO_DELAY_UDELAYis not set
#CONFIG_IO_DELAY_NONEis not setCONFIG_DEFAULT_IO_DELAY_TYPE=0
#CONFIG_DEBUG_BOOT_PARAMSis not set
#CONFIG_CPA_DEBUGis not set
#CONFIG_OPTIMIZE_INLININGis not set
#CONFIG_DEBUG_STRICT_USER_COPY_CHECKSis not set#
# Security options
#CONFIG_KEYS=yCONFIG_KEYS_DEBUG_PROC_KEYS=yCONFIG_SECURITY=y
#CONFIG_SECURITYFSis not setCONFIG_SECURITY_NETWORK=y
#CONFIG_SECURITY_NETWORK_XFRMis not set
#CONFIG_SECURITY_PATHis not set
#CONFIG_SECURITY_TOMOYOis not set
#CONFIG_SECURITY_APPARMORis not set
#CONFIG_IMAis not setCONFIG_DEFAULT_SECURITY_DAC=yCONFIG_DEFAULT_SECURITY=""CONFIG_CRYPTO=y#
# Crypto core or helper
#CONFIG_CRYPTO_ALGAPI=yCONFIG_CRYPTO_ALGAPI2=yCONFIG_CRYPTO_AEAD2=yCONFIG_CRYPTO_BLKCIPHER=yCONFIG_CRYPTO_BLKCIPHER2=yCONFIG_CRYPTO_HASH=yCONFIG_CRYPTO_HASH2=yCONFIG_CRYPTO_RNG2=yCONFIG_CRYPTO_PCOMP2=yCONFIG_CRYPTO_MANAGER=yCONFIG_CRYPTO_MANAGER2=yCONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
#CONFIG_CRYPTO_GF128MULis not set
#CONFIG_CRYPTO_NULLis not setCONFIG_CRYPTO_WORKQUEUE=y
#CONFIG_CRYPTO_CRYPTDis not set
#CONFIG_CRYPTO_AUTHENCis not set#
# Authenticated Encryption with Associated Data
#
#CONFIG_CRYPTO_CCMis not set
#CONFIG_CRYPTO_GCMis not set
#CONFIG_CRYPTO_SEQIVis not set#
# Block modes
#CONFIG_CRYPTO_CBC=y
#CONFIG_CRYPTO_CTRis not set
#CONFIG_CRYPTO_CTSis not setCONFIG_CRYPTO_ECB=y
#CONFIG_CRYPTO_LRWis not setCONFIG_CRYPTO_PCBC=y
#CONFIG_CRYPTO_XTSis not set#
# Hash modes
#CONFIG_CRYPTO_HMAC=y
#CONFIG_CRYPTO_XCBCis not set
#CONFIG_CRYPTO_VMACis not set#
# Digest
#CONFIG_CRYPTO_CRC32C=yCONFIG_CRYPTO_CRC32C_INTEL=y
#CONFIG_CRYPTO_GHASHis not set
#CONFIG_CRYPTO_MD4is not setCONFIG_CRYPTO_MD5=y
#CONFIG_CRYPTO_MICHAEL_MICis not set
#CONFIG_CRYPTO_RMD128is not set
#CONFIG_CRYPTO_RMD160is not set
#CONFIG_CRYPTO_RMD256is not set
#CONFIG_CRYPTO_RMD320is not setCONFIG_CRYPTO_SHA1=y
#CONFIG_CRYPTO_SHA256is not set
#CONFIG_CRYPTO_SHA512is not set
#CONFIG_CRYPTO_TGR192is not set
#CONFIG_CRYPTO_WP512is not set
#CONFIG_CRYPTO_GHASH_CLMUL_NI_INTELis not set#
# Ciphers
#
#CONFIG_CRYPTO_AESis not set
#CONFIG_CRYPTO_AES_X86_64is not set
#CONFIG_CRYPTO_AES_NI_INTELis not set
#CONFIG_CRYPTO_ANUBISis not set
#CONFIG_CRYPTO_ARC4is not set
#CONFIG_CRYPTO_BLOWFISHis not set
#CONFIG_CRYPTO_CAMELLIAis not set
#CONFIG_CRYPTO_CAST5is not set
#CONFIG_CRYPTO_CAST6is not set
#CONFIG_CRYPTO_DESis not set
#CONFIG_CRYPTO_FCRYPTis not set
#CONFIG_CRYPTO_KHAZADis not set
#CONFIG_CRYPTO_SALSA20is not set
#CONFIG_CRYPTO_SALSA20_X86_64is not set
#CONFIG_CRYPTO_SEEDis not set
#CONFIG_CRYPTO_SERPENTis not set
#CONFIG_CRYPTO_TEAis not set
#CONFIG_CRYPTO_TWOFISHis not set
#CONFIG_CRYPTO_TWOFISH_X86_64is not set#
# Compression
#
#CONFIG_CRYPTO_DEFLATEis not set
#CONFIG_CRYPTO_ZLIBis not set
#CONFIG_CRYPTO_LZOis not set#
# Random Number Generation
#
#CONFIG_CRYPTO_ANSI_CPRNGis not setCONFIG_CRYPTO_HW=y
#CONFIG_CRYPTO_DEV_PADLOCKis not set
#CONFIG_CRYPTO_DEV_HIFN_795Xis not setCONFIG_HAVE_KVM=y
#CONFIG_VIRTUALIZATIONis not setCONFIG_BINARY_PRINTF=y#
# Library routines
#CONFIG_BITREVERSE=yCONFIG_GENERIC_FIND_FIRST_BIT=yCONFIG_GENERIC_FIND_NEXT_BIT=yCONFIG_GENERIC_FIND_LAST_BIT=y
#CONFIG_CRC_CCITTis not set
#CONFIG_CRC16is not setCONFIG_CRC_T10DIF=y
#CONFIG_CRC_ITU_Tis not setCONFIG_CRC32=y
#CONFIG_CRC7is not setCONFIG_LIBCRC32C=yCONFIG_ZLIB_INFLATE=yCONFIG_ZLIB_DEFLATE=yCONFIG_LZO_DECOMPRESS=yCONFIG_DECOMPRESS_GZIP=yCONFIG_DECOMPRESS_BZIP2=yCONFIG_DECOMPRESS_LZMA=yCONFIG_DECOMPRESS_LZO=yCONFIG_HAS_IOMEM=yCONFIG_HAS_IOPORT=yCONFIG_HAS_DMA=yCONFIG_NLATTR=y
Signature · 4 lines
Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
Quoted 1 line · * Mathieu Desnoyers ([email protected]) wrote:
* Ingo Molnar ([email protected]) wrote:
[...]
Quoted 9 lines
Quoted 2 lines
I.e. please re-phrase your series as: "what else does it give us beyond tuning down the minimum granularity to 33% of its current value?"
That's indeed the nice way to phrase the question. So the added value of my approach is that I don't change the granularity when there are 3 or less tasks running on the system. So, with Peter's approach, I expect that the system throughput will be lower in this scenario, but my approach should keep it at pretty much the same values as the vanilla kernel.
Quoted 3 lines
But you are right, I should put some performance measurements too. Let me do a few test runs (I plan to use tbench) and come back with the measurements with
nr_running<= 3 for both Peter's approach and mine.
It turns out that tbench is rather more latency-sensitive than throughput-sensitive :
tbench 1, on UP 2.0GHz
* Mainline 2.6.35.2 kernel
Throughput 184.875 MB/sec 1 clients 1 procs max_latency=12.158 ms
* With my patches (dynamic granularity)
Throughput 185.99 MB/sec 1 clients 1 procs max_latency=14.683 ms
* With Peter's approach (smaller granularity)
Throughput 188.784 MB/sec 1 clients 1 procs max_latency=8.061 ms
So as we can see, my approach has a behavior that's much closer to mainline, but the tbench workload seems to favor smaller granularity here. I'm open to ideas about benchmarks that would test throughput without being so sensitive to latency.
Thanks,
Mathieu
Signature · 4 lines
Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
RFC PATCH 2/2 sched: sleepers coarse granularity on wakeup
In reply to Mathieu DesnoyersKeep a larger granularity for awakened sleepers, so the "FAIR_SLEEPER" feature is not affected by shrinking granularity.
--- include/linux/sched.h | 1 + kernel/sched.c | 1 + kernel/sched_debug.c | 1 + kernel/sched_fair.c | 11 +++++++++++ 4 files changed, 14 insertions(+)
kernel/sched_fair.c +11 -0
@@ -70,6 +70,11 @@ static unsigned int sched_nr_latency = 3static unsigned int sched_nr_latency_max =8 ;/* +* Runtime slice given to awakened sleepers. +*/ +unsigned int sysctl_sched_sleeper_wakeup_slice =2000000ULL ; + +/* * After fork, child runs first. If set to 0 (default) then * parent will (try to) run first. */
@@ -765,6 +770,7 @@ place_entity(struct cfs_rq *cfs_rq, stru thresh >>=1 ; vruntime -= thresh; + se->sleeper_wakeup_slice = sysctl_sched_sleeper_wakeup_slice; }/* ensure we never gain time by being placed backwards. */
@@ -881,6 +887,11 @@ check_preempt_tick(struct cfs_rq *cfs_rqif (!sched_feat (WAKEUP_PREEMPT ))return ; +if (delta_exec < curr->sleeper_wakeup_slice) +return ; +else + curr->sleeper_wakeup_slice =0 ; +if (delta_exec <__sched_gran (cfs_rq->nr_running))return ;
include/linux/sched.h +1 -0
@@ -1132,6 +1132,7 @@ struct sched_entity {u64 prev_sum_exec_runtime;u64 nr_migrations; +unsigned long sleeper_wakeup_slice;#ifdef CONFIG_SCHEDSTATS struct sched_statistics statistics;
kernel/sched.c +1 -0
@@ -2422,6 +2422,7 @@ static void __sched_fork(struct task_str p->se.sum_exec_runtime =0 ; p->se.prev_sum_exec_runtime =0 ; p->se.nr_migrations =0 ; + p->se.sleeper_wakeup_slice =0 ;#ifdef CONFIG_SCHEDSTATS memset (&p->se.statistics,0 ,sizeof (p->se.statistics));
kernel/sched_debug.c +1 -0
@@ -334,6 +334,7 @@ static int sched_debug_show(struct seq_fPN (sysctl_sched_std_granularity);PN (sysctl_sched_wakeup_granularity);PN (sysctl_sched_child_runs_first); +PN (sysctl_sched_sleeper_wakeup_slice);P (sysctl_sched_features);#undef PN#undef P
Peter Zijlstra
maintainerYou found improved latencies with something like the below as well, right? Except your proglet needs timers to be special too iirc.
Thomas objected to 'special' wakeups, and I can fully appreciate why, but maybe we could try it anyway, its only a reasonably soft hint anyway.
( full series with changelogs at:
programming.kicks-ass.net/sekrit/sched-patches.tar.bz2 )
I'm currently running it on my laptop, and while spread is reasonably controlled, interactivity isn't too sucky, but its not too hot either.
(I did lower my min_gran to like 1/5th of latency)
--- drivers/input/evdev.c | 2 + include/linux/sched.h | 22 +++++-- kernel/sched.c | 8 +- kernel/sched_debug.c | 2 - kernel/sched_fair.c | 160 +++++++++++++++++++++++------------------------ kernel/sched_features.h | 13 ++--- 7 files changed, 107 insertions(+), 102 deletions(-)
drivers/input/evdev.c +2 -0
@@ -84,6 +84,7 @@ static void evdev_event(struct input_handle *handle, event.code = code; event.value = value; +sched_wake_interactive_enable ();rcu_read_lock (); client =rcu_dereference (evdev->grab);
@@ -96,6 +97,7 @@ static void evdev_event(struct input_handle *handle,rcu_read_unlock ();wake_up_interruptible (&evdev->wait); +sched_wake_interactive_disable (); }static int evdev_fasync (int fd,struct file *file,int on)
include/linux/sched.h +16 -6
@@ -1097,7 +1097,6 @@ struct sched_statistics {u64 block_start;u64 block_max;u64 exec_max; -u64 slice_max;u64 nr_migrations_cold;u64 nr_failed_migrations_affine;
@@ -1121,7 +1120,8 @@ struct sched_entity {struct load_weight load;/* for load-balancing */ struct rb_node run_node;struct list_head group_node; -unsigned int on_rq; + unsigned int on_rq : 1, + interactive : 1;u64 exec_start;u64 sum_exec_runtime;
@@ -1239,11 +1239,11 @@ struct task_struct { unsigned did_exec:1; unsigned in_execve:1; /* Tell the LSMs that the process is doing an* execve */ - unsigned in_iowait:1; - -/* Revert to default priority/policy when forking */ - unsigned sched_reset_on_fork:1; + unsigned sched_in_iowait :1; /* Called io_schedule() */ + unsigned sched_reset_on_fork :1; /* Revert to default priority/policy +* on fork */ + unsigned sched_wake_interactive:4; /* User driven wakeup */pid_t pid;pid_t tgid;
@@ -1506,6 +1506,16 @@ struct task_struct {#endif }; +static inline void sched_wake_interactive_enable (void ) +{ + current->sched_wake_interactive++; +} + +static inline void sched_wake_interactive_disable (void ) +{ + current->sched_wake_interactive--; +} +/* Future-safe accessor for struct task_struct's cpus_allowed. */ #define tsk_cpus_allowed (tsk) (&(tsk)->cpus_allowed)
kernel/sched.c +4 -4
@@ -5125,9 +5125,9 @@ void __sched io_schedule(void)delayacct_blkio_start ();atomic_inc (&rq->nr_iowait); - current->in_iowait =1 ; + current->sched_in_iowait =1 ;schedule (); - current->in_iowait =0 ; + current->sched_in_iowait =0 ;atomic_dec (&rq->nr_iowait);delayacct_blkio_end (); }
@@ -5140,9 +5140,9 @@ long __sched io_schedule_timeout(long timeout)delayacct_blkio_start ();atomic_inc (&rq->nr_iowait); - current->in_iowait =1 ; + current->sched_in_iowait =1 ; ret =schedule_timeout (timeout); - current->in_iowait =0 ; + current->sched_in_iowait =0 ;atomic_dec (&rq->nr_iowait);delayacct_blkio_end ();return ret;
kernel/sched_debug.c +0 -2
@@ -76,7 +76,6 @@ static void print_cfs_group_stats(struct seq_file *m, int cpu,PN (se->statistics.sleep_max);PN (se->statistics.block_max);PN (se->statistics.exec_max); -PN (se->statistics.slice_max);PN (se->statistics.wait_max);PN (se->statistics.wait_sum);P (se->statistics.wait_count);
@@ -408,7 +407,6 @@ void proc_sched_show_task(struct task_struct *p, struct seq_file *m)PN (se.statistics.sleep_max);PN (se.statistics.block_max);PN (se.statistics.exec_max); -PN (se.statistics.slice_max);PN (se.statistics.wait_max);PN (se.statistics.wait_sum);P (se.statistics.wait_count);
kernel/sched_fair.c +79 -81
281 lines not on this page · raw message
kernel/sched_features.h +5 -8
@@ -3,13 +3,14 @@* them to run sooner, but does not allow tons of sleepers to * rip the spread apart. */ +SCHED_FEAT(FAIR_SLEEPERS, 0)SCHED_FEAT (GENTLE_FAIR_SLEEPERS ,1 )/* * Place new tasks ahead so that they do not starve already running * tasks */ -SCHED_FEAT (START_DEBIT ,1 ) +SCHED_FEAT (START_DEBIT ,0 )/* * Should wakeups try to preempt running tasks.
@@ -25,13 +26,6 @@ SCHED_FEAT(WAKEUP_PREEMPT, 1)SCHED_FEAT (AFFINE_WAKEUPS ,1 )/* -* Prefer to schedule the task we woke last (assuming it failed -* wakeup-preemption), since its likely going to consume data we -* touched, increases cache locality. - */ -SCHED_FEAT (NEXT_BUDDY ,0 ) - -/* * Prefer to schedule the task that ran last (when we did * wake-preempt) as that likely will touch the same data, increases * cache locality.
@@ -55,6 +49,9 @@ SCHED_FEAT(LB_BIAS, 1) SCHED_FEAT(LB_SHARES_UPDATE, 1) SCHED_FEAT(ASYM_EFF_LOAD, 1) +SCHED_FEAT(DYN_MIN_VRUNTIME, 1) +SCHED_FEAT (INTERACTIVE ,1 ) +/* * Spin-wait on mutex acquisition when the mutex owner is running on * another cpu -- assumes that when the owner is running, it will soon