> OK, then it has the same speed as before - maybe a bit slower because of
> the additional redirection. The big advantage of the trick Bernd suggested
> is that it makes the system much more reliable. It is very bad when Linux
> stops forking because memory is fragmented.
a 'bit' slower?? "current" is one of the most frequently used variables in
the kernel. (in 2.1.108 it's used ~5780 times througout the kernel source)
bloats code, uses up L1 cache.
A 4k stack is not quite enough. it should be, but in RL it was pain and
caused way too common 'ayiee, stack corrupted ..' crashes. The current 7k
stack seems to be just about perfect, enough for all drivers/filesystems,
and still doesnt waste a full second page, because we have the task
structure there.
put yet another way, if we cannot allocate 8k pages more or less reliably,
we are dead for NFS serving anyway ... and if we cannot allocate 8k pages
in fork() [which can wait, unlike the IRQ handler] we are doing way too
bad work too :(
-- mingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html