[ros-dev] Re: [ros-svn] [hbirr] 15818: Allocate the section object
from non paged pool because the storage for a spin lock must be in non
w3seek at reactos.com
Mon Jun 6 21:33:54 CEST 2005
Alex Ionescu wrote:
> Not that I disagree with your changes (it seems they are necessary) but
> don't they imply a bigger architectural problem? I've checked with
> WinOBJ and the Section Object is allocated in paged memory... just
> wanted to let you know this is why I made the change.
Well, then probably the spinlock in the section object was replaced with
another synchronization object in newer releases of windows? The problem
is you cannot have a spinlock structure in paged memory because as soon
as you acquire it you assume it is paged in (which most probably will be
the case), but you also assume it doesn't get paged out in the meanwhile
(which is impossible on UP systems but could occur on SMP systems).
More information about the Ros-dev