parceque: (desole pour l'anglais)
Below is a patch to enable 4Kb kernel stacks for x86, based on David
Howells' earlier work.
The goal of enabling 4K kernel stacks is to
1) Reduce footprint per thread so that systems can run many more threads
(for the java people)
2) Reduce the pressure on the VM for order > 0 allocations. We see real life
workloads (granted with 2.4 but the fundamental fragmentation issue isn't
solved in 2.6 and isn't solvable in theory) where this can be a problem.
In addition order > 0 allocations can make the VM "stutter" and give more
latency due to having to do much more work trying to defragment
sén suit des commentaires assez interressant sur les fonctions inline qui augmentent la consomation en pile.
[^] # Pourquoi 4k?
Posté par Pierre . En réponse à la dépêche Nouveaux pilotes nvidia 6106. Évalué à 4.
Below is a patch to enable 4Kb kernel stacks for x86, based on David
Howells' earlier work.
The goal of enabling 4K kernel stacks is to
1) Reduce footprint per thread so that systems can run many more threads
(for the java people)
2) Reduce the pressure on the VM for order > 0 allocations. We see real life
workloads (granted with 2.4 but the fundamental fragmentation issue isn't
solved in 2.6 and isn't solvable in theory) where this can be a problem.
In addition order > 0 allocations can make the VM "stutter" and give more
latency due to having to do much more work trying to defragment
sén suit des commentaires assez interressant sur les fonctions inline qui augmentent la consomation en pile.
http://people.redhat.com/arjanv/4kstack.patch(...)