(Stack) Size Matters

re: (Stack) Size Matters

Steve Dispensa — Thu, 09 Sep 2004 13:49:00 GMT

where windows kernel services interrupts? On the current stack, or by switching to the "interrupt thread"? If the former, then effective stack size is actually smaller, because stack has to be shared between thread and interrupt.

It worth noting that Linux goes into opposite direction: in 2.6 (x86) kernel stack was reduced from 2 pages, to 1 page (4K).

re: (Stack) Size Matters

Steve Dispensa — Sun, 05 Sep 2004 14:54:00 GMT

No, any call to win32k does it. PsConvertToGuiThread is called on the first win32k system service and it switches the kernel stack to a large stack.

re: (Stack) Size Matters

Steve Dispensa — Sat, 04 Sep 2004 14:12:00 GMT

Skywing - I might be well wrong, but isn't the 64Kb stack the case only for threads that did *DirectDraw/3D* calls to win32k?

re: (Stack) Size Matters

Steve Dispensa — Wed, 01 Sep 2004 22:36:00 GMT

Actually the KM stack was changed from 2 pages to 3 page s between NT 3.51 and NT4 (at least on i386). The reason had something to do with filesystem reentrancy IIRC.

re: (Stack) Size Matters

Steve Dispensa — Mon, 30 Aug 2004 14:25:00 GMT

Note that threads that have called into win32k.sys will have larger stacks - 64K, IIRC.