Re: Thread stack allocation (was Re: cvs commit: src/lib/libc_r Makefile src/lib/libc_r/uthread pthread_private.h uthread_create.c uthread_gc.c uthread_init.c)

1999-07-13 Thread Alan Cox
On Mon, Jul 12, 1999 at 10:53:49PM +0400, Dmitrij Tejblum wrote: I don't see how MAP_ANON is better than MAP_STACK. It consumes fewer resources. Each time you grow the stack, it adds another vm_map_entry to the vm_map and (eventually) allocates another vm_object. Using MAP_ANON, there is

Re: Thread stack allocation (was Re: cvs commit: src/lib/libc_r Makefile src/lib/libc_r/uthread pthread_private.h uthread_create.c uthread_gc.c uthread_init.c)

1999-07-12 Thread Dmitrij Tejblum
On Mon, 12 Jul 1999, Dmitrij Tejblum wrote: Alan Cox wrote: When you create a stack or grow an existing stack, the minimum chunk size is 128K. This make use of "growable" stacks in libc_r particulary useful, given that libc_r make "growable" only 64K stacks. That is a problem,