Make max_threads be based on normal zone size
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 8 lines · Dave McCracken
The
max_threadsconfig parameter (used to determine how many tasks to allow) is currently calculated based on the total amount of physical memory in the machine. This is wrong, since the real limiting factor is the amount of memory in the normal zone.This patch fixes the initialization of
max_threadsby allowing an architecture to specify how much memory is in the normal zone, and using that value to initializemax_threads.
There are lots of other functions with the same problem (like all the hash table sizing and others). Perhaps these should be fixed too?
-Andi
Quoted 2 lines · --On Friday, March 01, 2002 19:14:41 +0100 Andi Kleen <[email protected]> wrote:
There are lots of other functions with the same problem (like all the hash table sizing and others). Perhaps these should be fixed too?
I coded the patch in a fashion that makes both total physical memory and mapped physical memory size available, specifically so other people could change places that might also have the same problem. I guessed there might be some.
Dave McCracken
======================================================================
Dave McCracken IBM Linux Base Kernel Team 1-512-838-3059
[email protected] T/L 678-3059