Hi,
I've still more problems with the modifications in the virtual memory functions. My test case is ctm from rosapps. It shows the cpu time and memory usage of the processes. While waiting for a keyboard event, ctm (kernel32) destroys and creates every 100ms a new thread. It seems, that the memory (teb, stack, ...) isn't freed. The thread itself is destroyed. Ps shows always two threads for ctm.
- Hartmut
-----Original Message----- From: ros-dev-bounces@reactos.com [mailto:ros-dev-bounces@reactos.com] On Behalf Of Ge van Geldorp Sent: Friday, October 01, 2004 10:46 PM To: 'ReactOS Development List' Subject: [ros-dev] TEB spacing
From: Ge van Geldorp
From: Hartmut Birr
this patch (or some areas in ntoskrnl) isn't correct. This patch puts always 64kB between the TEB's. This limits the number of threads to 30,000 or less. I've found this by an other bug in kernel32.
Yes, you're right, that is an unwanted side effect. I think I'll change the TEB allocation to reserve 64k at a time and then commit 4k for each TEB, so we can have TEBs spaced tightly together again.
This is now implemented. I've successfully created and destroyed 600000 threads in a single process, so we should be ok I guess.
Ge van Geldorp.
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev