Export (0) Print
Expand All

MM_ALLOCATE_XXX

The MM_ALLOCATE_XXX constants are flag bits that specify how the MmAllocatePagesForMdlEx routine allocates pages.

Constant/valueDescription
MM_DONT_ZERO_ALLOCATION
0x00000001

Do not fill the allocated pages with zeros. By default, MmAllocatePagesForMdlEx zeros the pages that it allocates. By skipping this operation, you can potentially improve the performance of the MmAllocatePagesForMdlEx call. However, you must not use this flag unless either you never expose the allocated pages to user-mode programs, or you always overwrite the original contents of the pages before you expose the allocated pages to user-mode programs.

MM_ALLOCATE_FROM_LOCAL_NODE_ONLY
0x00000002

Allocate pages only from the ideal node. This flag applies only to multiprocessor systems that have non-uniform memory access (NUMA) architectures. Starting with Windows Vista, this flag indicates that all pages must be allocated from the ideal node of the current thread. No pages are to be allocated from other nodes. In versions of Windows earlier than Windows Vista, this flag indicates that all pages must be allocated from the local node; that is, from the node that the current processor belongs to. For more information about NUMA multiprocessor systems, see NUMA Support.

MM_ALLOCATE_FULLY_REQUIRED
0x00000004

A full allocation is required. Starting with Windows 7, this flag requires MmAllocatePagesForMdlEx to return NULL if it cannot allocate all the requested pages. The routine returns a non-NULL value only if it successfully obtains the entire requested allocation. This flag enables the memory manager to perform the allocation more efficiently in cases in which the caller requires a full allocation.

MM_ALLOCATE_NO_WAIT
0x00000008

Do not wait. Starting with Windows 7, this flag indicates that the MmAllocatePagesForMdlEx call must not block the calling thread. Typically, the caller is a kernel-mode driver that is running at IRQL < DISPATCH_LEVEL but cannot allow its execution to be blocked. For example, the driver might be assisting with paging or power-management operations. Regardless of whether this flag is set, MmAllocatePagesForMdlEx never blocks callers that are running at IRQL = DISPATCH_LEVEL.

MM_ALLOCATE_PREFER_CONTIGUOUS
0x00000010

Allocation is performed in a way that minimizes system memory fragmentation. Starting with Windows 7, this flag indicates that the caller wants to avoid fragmenting physical memory to make more contiguous memory available to other callers. The allocated pages are not guaranteed to be (and usually are not) physically contiguous, even if plenty of contiguous memory is available. Callers that require contiguous memory should specify MM_ALLOCATE_REQUIRE_CONTIGUOUS_CHUNKS instead of MM_ALLOCATE_PREFER_CONTIGUOUS.

MM_ALLOCATE_REQUIRE_CONTIGUOUS_CHUNKS
0x00000020

Contiguous memory is required. Starting with Windows 7, this flag indicates that the requested pages must be allocated as contiguous blocks of physical memory. If the SkipBytes parameter is zero, MmAllocatePagesForMdlEx either succeeds and returns a single, contiguous block, or it fails and returns NULL. It never returns a partial allocation. For SkipBytes = 0, the allocated pages satisfy the address range requirements that are specified by the LowAddress and HighAddress parameters, but the pages are subject to no special alignment restrictions. If SkipBytes is nonzero, SkipBytes must be a power of two and must be greater than or equal to PAGE_SIZE, and the TotalBytes parameter value must be a multiple of SkipBytes. In this case, the returned MDL can contain multiple blocks of contiguous pages. That is, each block is internally contiguous but the blocks are not necessarily contiguous with each other. Each block of contiguous pages is guaranteed to be exactly SkipBytes long and to be aligned on a SkipBytes boundary. Partial allocations can occur if SkipBytes is nonzero, but each contiguous block in a partial allocation is guaranteed to be SkipBytes long.

Remarks

The MM_DONT_ZERO_ALLOCATION or MM_ALLOCATE_FROM_LOCAL_NODE_ONLY flags are supported starting with Windows Server 2003 with Service Pack 1 (SP1).

The following MM_ALLOCATE_XXX flags are supported starting with Windows 7:

  • MM_ALLOCATE_FULLY_REQUIRED
  • MM_ALLOCATE_NO_WAIT
  • MM_ALLOCATE_PREFER_CONTIGUOUS
  • MM_ALLOCATE_REQUIRE_CONTIGUOUS_CHUNKS

Requirements

Version

See Remarks section.

Header

Wdm.h (include Wdm.h, Ntddk.h, or Ntifs.h)

See also

MmAllocatePagesForMdlEx

 

 

Send comments about this topic to Microsoft

Show:
© 2014 Microsoft