GEOS SDK TechDocs
|
|
2.3 Virtual Memory Blocks
|
3 Using Virtual Memory
VMAttributes
Each VM file has a set of attributes which determine how the VM Manager treats the file. These attributes are specified by a set of
VMAttributes
flags. When a VM file is created, all of these attributes are off; after a file has been created, you can change the attributes with
VMSetAttributes()
(see Changing VM File Attributes
). The following flags are available:
VMUpdate()
,
VMSave()
, etc.). This attribute is
off
by default (indicating that the VM manager should feel free to update blocks whenever they are unlocked). You should set this attribute if the file might not be in a consistent state every time a block is unlocked.
MSG_META_VM_FILE_DIRTY
to each process that has the file open. (This message is defined for
MetaClass
, so any object can handle it.)
OLMBH_inUseCount
is non-zero. This attribute must be set if the file contains object blocks. If this attribute is set, each object block will be kept in memory as long as any thread is using an object in the block.
CompactObjBlock()
. This allows a VM file to contain generic object blocks.
VMLock()
. This attribute must be set if the VM file contains object blocks.
GEOS SDK TechDocs
|
|
2.3 Virtual Memory Blocks
|
3 Using Virtual Memory