Searched refs:setPurgeable (Results 1 - 4 of 4) sorted by relevance
| /macosx-10.10.1/xnu-2782.1.97/iokit/Kernel/ |
| H A D | IOSubMemoryDescriptor.cpp | 133 IOReturn IOSubMemoryDescriptor::setPurgeable( IOOptionBits newState, function in class:IOSubMemoryDescriptor
138 err = _parent->setPurgeable( newState, oldState );
|
| H A D | IOMemoryDescriptor.cpp | 2536 IOGeneralMemoryDescriptor::setPurgeable( IOOptionBits newState, function in class:IOGeneralMemoryDescriptor
2546 err = super::setPurgeable(newState, oldState);
2597 IOReturn IOMemoryDescriptor::setPurgeable( IOOptionBits newState, function in class:IOMemoryDescriptor
|
| /macosx-10.10.1/xnu-2782.1.97/iokit/IOKit/ |
| H A D | IOSubMemoryDescriptor.h | 93 virtual IOReturn setPurgeable( IOOptionBits newState,
|
| H A D | IOMemoryDescriptor.h | 250 /*! @function setPurgeable
252 @discussion Buffers may be allocated with the ability to have their purgeable status changed - IOBufferMemoryDescriptor with the kIOMemoryPurgeable option, VM_FLAGS_PURGEABLE may be passed to vm_allocate() in user space to allocate such buffers. The purgeable status of such a buffer may be controlled with setPurgeable(). The process of making a purgeable memory descriptor non-volatile and determining its previous state is atomic - if a purgeable memory descriptor is made nonvolatile and the old state is returned as kIOMemoryPurgeableVolatile, then the memory's previous contents are completely intact and will remain so until the memory is made volatile again. If the old state is returned as kIOMemoryPurgeableEmpty then the memory was reclaimed while it was in a volatile state and its previous contents have been lost.
264 virtual IOReturn setPurgeable( IOOptionBits newState,
1039 virtual IOReturn setPurgeable( IOOptionBits newState,
|
Completed in 367 milliseconds