Hi Gunnar,
gdalsnes@svn.reactos.com wrote:
make classes use session wide atom table. should fix bug 899
Added files: trunk/reactos/subsys/win32k/ntuser/session.c
What are you plans for managing multiple instances of win32k.sys?
what would be the point of multiple instances of win32k.sys. I thought once it is loaded into memory by the kernel it isn't needed until reboot. That was my understanding anyway... On Oct 13, 2005, at 6:32 PM, Emanuele Aliberti wrote:
Hi Gunnar,
gdalsnes@svn.reactos.com wrote:
make classes use session wide atom table. should fix bug 899
Added files: trunk/reactos/subsys/win32k/ntuser/session.c
What are you plans for managing multiple instances of win32k.sys?
-- :Emanuele Aliberti
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Rick Langschultz rlangschultz@cox.net (Home) rlangschultz@ellemaespa.com (Work) rlangschultz@email.uophx.edu (School)
No plans. I just thought we missed a session.c in there;-P
About multiple win32k instances: It will only be loaded into mem once and mapped into each session. Each session will get a copy of win32k's data segment. That shouldnt require that much memory? Afaik, win32k is totally(?) session unaware. Session = win32k code segment mapping + win32k data segment copy + csrss + winlogon etc.
I found this strange stuff btw: http://www.ncisive.com/PDFs/GGXP%2021%20Architecture.pdf. Some lightweight session stuff?
G.
Emanuele Aliberti wrote:
Hi Gunnar,
gdalsnes@svn.reactos.com wrote:
make classes use session wide atom table. should fix bug 899
Added files: trunk/reactos/subsys/win32k/ntuser/session.c
What are you plans for managing multiple instances of win32k.sys?