[ros-dev] gdi object code optimization

Timo Kreuzer timo.kreuzer at web.de
Fri Dec 14 15:14:30 CET 2007


I have started with a new deleting mechanism, wich is the way it works
on windows, see
http://www.reactos.org/wiki/index.php/Techwiki/win32k/gdiobjects

After that I'd like to change the allocation of objects to
XXXOBJ_AllocObj -> allocates only the memory and initializes it
GDIOBJ_CreateHandle -> inserts the object into the handle table, only
when neccessary
GDIOBJ_FreeHandle -> removes the object from the handle table
XXXOBJ_FreeObj -> frees the memory and performs cleanup

XXXOBJ_Xxx function will then use pointers to the data structures only
and we can stop that massive locking unlocking in most cases.


Can you explain your ideas? Where is it incompatible?

James Tabor schrieb:
> Hi!
> Let us start on this now.... It is time to restructure the GDI OBJ
> Lock Unlock mess! Don't wait for me.
> I'm working on the DCE issue which is a mess due to gdiobj.c over
> think object locking system. The new
> ideas I have will not be compatible with the current system.
> Thanks,
> James
> _______________________________________________
> Ros-dev mailing list
> Ros-dev at reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>   



More information about the Ros-dev mailing list