| 术语 | createfilemapping |
| 释义 | CreateFileMapping 语法： C++ HANDLE WINAPI CreateFileMapping( __in HANDLE hFile, __in_opt LPSECURITY_ATTRIBUTES lpAttributes, __in DWORD flProtect, __in DWORD dwMaximumSizeHigh, __in DWORD dwMaximumSizeLow, __in_opt LPCTSTR lpName ); CreateFileMapping函数 创建或打开一个有名或无名的文件指定文件映射对象。 要指定的物理内存NUMA节点，见CreateFileMappingNuma。 参数 hFile [in] 句柄的文件中，创建一个文件映射对象。 该文件必须开放访问的权利与保护标志的flProtect参数指定兼容。 It is not required, but it is recommended that files you intend to map be opened for exclusive access.有关更多信息，请参阅文件安全性和访问权限。 如果hFile是INVALID_HANDLE_VALUE，调用进程也必须指定一个在dwMaximumSizeHigh和dwMaximumSizeLow参数文件映射对象的大小。在这种情况下，CreateFileMapping创建一个指定大小，由系统分页文件的支持，而不是由一个在文件系统中文件的文件映射对象。 lpAttributes [中，可选] 一个 SECURITY_ATTRIBUTES结构，决定是否返回的句柄可以被继承的子进程的指针。 如果lpAttributes为NULL，则句柄不能被继承。 这个结构的lpSecurityDescriptor成员指定一个新的文件映射对象的安全描述符。如果lpAttributes为NULL，则文件映射对象得到一个默认安全描述符。访问控制列表中的一个文件映射默认安全描述符(ACL)的对象是来自小学或模拟令牌的创造者。有关更多信息，请参阅文件映射安全和访问权限。 flProtect [in] 指定文件映射对象的页面保护。对象映射的所有意见必须符合这种保护。 此参数可以是下列值之一。 ValueMeaning PAGE_EXECUTE_READAllows意见映射为读只，复制上写字，或执行访问。 文件句柄指定的hFile参数必须与GENERIC_READ和GENERIC_EXECUTE访问权限创建。 Windows Server 2003和Windows XP中：此值才带有SP2的Windows和Windows Server 2003 XP的SP1的可用。 Windows 2000中：此值不支持。 PAGE_EXECUTE_READWRITEAllows意见映射为读只，复制，上写，读/写，或执行访问。 文件句柄的hFile参数指定要与GENERIC_READ，GENERIC_WRITE创建和GENERIC_EXECUTE访问权限。 Windows Server 2003和Windows XP中：此值才带有SP2的Windows和Windows Server 2003 XP的SP1的可用。 Windows 2000中：此值不支持。 PAGE_EXECUTE_WRITECOPYAllows意见映射为读只，复制上写字，或执行访问。此值等于PAGE_EXECUTE_READ。 文件句柄的hFile参数指定必须以GENERIC_READ和GENERIC_EXECUTE访问权限创建。 Windows Server 2003和Windows XP/2000操作系统：此值不支持。 Windows Vista的：此值不带有SP1，直到Windows Vista中可用。 PAGE_READONLYAllows意见为读映射的或复制的写访问。试图写入访问冲突的特定区域的结果。 文件句柄的hFile参数指定，必须与GENERIC_READ访问权限创建。 PAGE_READWRITEAllows意见映射为读只，复制，上写，或读/写访问。 文件句柄的hFile参数指定必须以GENERIC_READ和GENERIC_WRITE访问权限创建。 PAGE_WRITECOPYAllows意见为读映射的或复制的写访问。此值等于PAGE_READONLY。 文件句柄的hFile参数指定，必须与GENERIC_READ访问权限创建。 一个应用程序可以指定相结合前面的页面保护价值逐一或该文件映射对象的下列属性。 ValueMeaning SEC_COMMITIf文件映射对象是由操作系统支持分页文件(即hfile参数INVALID_HANDLE_VALUE)，规定在该文件的视图映射到进程地址空间，页面的整个范围，而不是致力于保留。该系统必须有足够的承付页容纳整个映射。 Otherwise, CreateFileMapping fails. 没有这个属性的文件映射是可执行图像文件或数据文件备份对象效应(hfile参数是一个句柄文件)。 SEC_COMMIT不能结合SEC_RESERVE。 如果指定没有属性，SEC_COMMIT假设。 SEC_IMAGESpecifies该文件的hFile参数指定是一个可执行映像文件。 由于地图资料和文件保护取自图像文件，没有其他属性与SEC_IMAGE有效。 SEC_LARGE_PAGESEnables大页面被映射的文件是由操作系统的分页文件备份对象使用(hfile参数INVALID_HANDLE_VALUE)。此属性不支持文件映射的是可执行图像文件或数据文件备份对象(hFile参数是一个句柄，可执行图像或数据文件)。 该文件映射对象的最大大小必须是由GetLargePageMinimum函数返回一个大页面的最小尺寸的倍数。如果不是，CreateFileMapping失败。当映射文件映射视图对象SEC_LARGE_PAGES创建，基地地址和视图的大小也必须最低大页面大小的倍数。 SEC_LARGE_PAGES要求SeLockMemoryPrivilege权限将在调用方的令牌启用。 如果SEC_LARGE_PAGES指定，SEC_COMMIT还必须指定。 Windows Server 2003中：此值不直到Windows Server 2003 SP1的支持。 Windows XP/2000操作系统：此值不支持。 SEC_NOCACHESets所有网页为非被缓存。 应用程序不应使用，除非明确的设备所需的此属性。 Using the interlocked functions with memory that is mapped with SEC_NOCACHE can result in an EXCEPTION_ILLEGAL_INSTRUCTION exception. SEC_NOCACHE，必须在SEC_RESERVE或SEC_COMMIT属性进行设置。 SEC_RESERVEIf文件映射对象是由操作系统支持分页文件(即hfile参数INVALID_HANDLE_VALUE)，规定在该文件的视图映射到进程地址空间，页面的整个范围，供日后使用过程中保留而不是承诺。 保留页可以承诺的后续调用VirtualAlloc函数。后页承诺，它们不能被释放或与decommitted VirtualFree函数。 没有这个属性的文件映射是可执行图像文件或数据文件备份对象效应(hfile参数是一个句柄文件)。 SEC_RESERVE不能结合SEC_COMMIT。 SEC_WRITECOMBINESets所有网页被写结合起来。 应用程序不应使用，除非明确的设备所需的此属性。使用内存映射与SEC_WRITECOMBINE可能会导致异常的EXCEPTION_ILLEGAL_INSTRUCTION互锁功能。 SEC_WRITECOMBINE，必须在SEC_RESERVE或SEC_COMMIT属性进行设置。 Windows Server 2003和Windows XP/2000操作系统：这个标志是不支持，直到Windows Vista的。 dwMaximumSizeHigh [in] 高阶双字节值对文件映射对象的最大尺寸。 dwMaximumSizeLow [in] 在低位双字节值对文件映射对象的最大尺寸。 如果这个参数和dwMaximumSizeHigh为0(零)，该文件映射对象的最大大小等于该文件hFile确定的当前大小。 试图映射的长度为0(零)文件失败的ERROR_FILE_INVALID错误代码。应该测试应用程序的文件的长度为0(零)和拒绝这些文件。 lpName [中，可选] 该文件映射对象的名称。 如果此参数匹配现有的映射对象的名称，功能请求访问与保护flProtect指定对象。 如果该参数为NULL，则文件映射对象被创建没有名称。 如果lpName匹配现有的事件，信号量，互斥体，可等待定时器，或工作对象的名称，功能失败，并且GetLastError函数返回出现ERROR_INVALID_HANDLE。这是因为这些对象共享相同的命名空间。 终端服务：名称可以有一个“全球\\”或“Local \\”前缀明确创建对象的全局或会话命名空间。名称的其余部分可以包含以外的任何字符反斜杠字符(\\)。创建一个会话比从零的会议，在全局命名文件映射对象需要SeCreateGlobalPrivilege特权。如需信息见命名内核对象。 Windows XP中：快速用户切换是通过使用终端服务会话。第一个用户对使用记录会话0(零)，下次用户登录使用会话1(一)，等等。内核对象名称必须按照概述为终端服务，使应用程序能够支持多个用户指南。 Windows 2000的：如果终端服务没有运行，“全球\\”和“地方\\”前缀将被忽略。名称的其余部分可以包含反斜杠以外的任何字符的字符。 返回值 如果函数成功，返回值是一个句柄到新创建的文件映射对象。 如果该对象在函数调用之前存在，函数返回的句柄现有的对象(其目前的规模，而不是指定的大小)，GetLastError返回ERROR_ALREADY_EXISTS。 如果函数失败，返回值为NULL。为了获得更多错误信息，调用GetLastError。 备注 后一个文件映射对象被创建时，文件的大小不得超过该文件映射对象的大小，如果不，不是文件的内容都可以共享。 如果应用程序指定一个文件映射对象大于实际命名的磁盘上的文件大小，如果页面保护允许写访问(即flProtect参数指定PAGE_READWRITE或PAGE_EXECUTE_READWRITE)，然后在磁盘上的文件的大小增加匹配的文件映射对象指定的大小。如果该文件的延长，之间的文件的旧的结束和新的档案文件的末尾的内容不能保证为零;的行为是由文件系统定义。如果磁盘上的文件不能增加，CreateFileMapping失败，GetLastError返回ERROR_DISK_FULL。 在一个文件映射的网页对象的初始内容由操作系统支持分页文件是0(零)。 在处理这CreateFileMapping返回充分接触到一个新的文件映射对象，可以用任何功能，需要处理的文件映射对象使用。 多个进程可以共享通过使用一个单一的共享文件映射对象或创建单独的文件映射同一文件支持的对象是相同的文件视图。单个文件映射对象可以被多个进程共享的通过继承的过程中创造处理，重复处理，或打开档案的名称映射对象。 For more information, see the CreateProcess , DuplicateHandle and OpenFileMapping functions. 创建一个文件映射对象不实际映射到进程地址空间看法。该MapViewOfFile和MapViewOfFileEx功能映射一个文件到进程地址空间看法。 一个重要的例外，文件从任何文件映射对象，由同一个文件备份所得的意见一致或相同的在特定时间。一致性保证在一个进程和意见，是代表不同的进程映射的意见。 唯一的例外是有关远程文件。虽然与远程文件CreateFileMapping的作品，它没有让他们一致的。例如，如果两台计算机都映射到可写的文件，都改变同一页上，每一台计算机上只能看到自己写的网页。当数据在磁盘上得到更新，这不是合并。 阿映射文件和通过使用输入和输出(I / O)的功能(ReadFile和WriteFile)访问的文件不一定是一致的。 映射的意见文件映射对象保持与对象的内部参考，和一个文件映射对象不关闭，直到所有对它的引用被释放。因此，要完全关闭一个文件映射对象，应用程序必须通过调用UnmapViewOfFile取消映射并关闭该文件映射对象句柄调用CloseHandle的文件映射对象映射的所有意见。这些函数可以调用任何顺序排列。 创建一个会话比从零的会议，在全局命名文件映射对象需要SeCreateGlobalPrivilege特权。请注意，此特权检查仅限于文件映射对象的创建，不适用于现有的开放。例如，如果一个服务或系统创建一个全局命名空间中的文件映射对象，任何进程在任何会话中运行的可以访问该文件映射对象提供来电者具有所需的访问权限。 Windows XP/2000操作系统：上段中所述的规定，是带有SP2和Windows 2000 Server含Service Pack 4(SP4的与Windows Server 2003，Windows XP中) 使用为结构异常处理保护任何代码写入或读取一个文件视图。有关详细信息，请阅读并从文件视图写作。 有一个具有执行权限的映射，应用程序必须调用要么PAGE_EXECUTE_READWRITE或PAGE_EXECUTE_READ CreateFileMapping，然后调用FILE_MAP_EXECUTE MapViewOfFile | FILE_MAP_WRITE或FILE_MAP_EXECUTE | FILE_MAP_READ。 实例 有关示例，请参阅创建命名共享内存或创建一个文件映射使用大页。 要求： 最低支持：client－Windows 2000专业版 最低支持server－Windows 2000服务器 HeaderWinbase.h(头文件：winuser.h) LibraryKernel32.lib DLLKernel32.dll Unicode和ANSI namesCreateFileMappingW(Unicode)和CreateFileMappingA(ANSI)的 参见 CloseHandle CreateFileMappingNuma 创建一个文件映射对象 DuplicateHandle 文件映射函数 MapViewOfFile MapViewOfFileEx OpenFileMapping ReadFile SECURITY_ATTRIBUTES UnmapViewOfFile VirtualAlloc WriteFile 如果有任何问题和意见，请发送给微软(wsddocfb@microsoft.com) 生成日期：2009年8月27日 ＝＝英文原文＝＝CreateFileMapping Function Creates or opens a named or unnamed file mapping object for a specified file. To specify the NUMA node for the physical memory, see CreateFileMappingNuma . Syntax C++ HANDLE WINAPI CreateFileMapping( __in HANDLE hFile, __in_opt LPSECURITY_ATTRIBUTES lpAttributes, __in DWORD flProtect, __in DWORD dwMaximumSizeHigh, __in DWORD dwMaximumSizeLow, __in_opt LPCTSTR lpName ); Parameters hFile [in] A handle to the file from which to create a file mapping object. The file must be opened with access rights that are compatible with the protection flags that the flProtect parameter specifies. It is not required, but it is recommended that files you intend to map be opened for exclusive access. For more information, see File Security and Access Rights . If hFile is INVALID_HANDLE_VALUE, the calling process must also specify a size for the file mapping object in the dwMaximumSizeHigh and dwMaximumSizeLow parameters. In this scenario, CreateFileMapping creates a file mapping object of a specified size that is backed by the system paging file instead of by a file in the file system. lpAttributes [in, optional] A pointer to a SECURITY_ATTRIBUTES structure that determines whether a returned handle can be inherited by child processes. If lpAttributes is NULL, the handle cannot be inherited. The lpSecurityDescriptor member of this structure specifies a security descriptor for a new file mapping object. If lpAttributes is NULL, the file mapping object gets a default security descriptor. The access control lists (ACL) in the default security descriptor for a file mapping object come from the primary or impersonation token of the creator. For more information, see File Mapping Security and Access Rights . flProtect [in] Specifies the page protection of the file mapping object. All mapped views of the object must be compatible with this protection. This parameter can be one of the following values. ValueMeaning PAGE_EXECUTE_READAllows views to be mapped for read-only, copy-on-write, or execute access. The file handle specified by the hFile parameter must be created with the GENERIC_READ and GENERIC_EXECUTE access rights. Windows Server 2003 and Windows XP: This value is not available until Windows XP with SP2 and Windows Server 2003 with SP1. Windows 2000: This value is not supported. PAGE_EXECUTE_READWRITEAllows views to be mapped for read-only, copy-on-write, read/write, or execute access. The file handle that the hFile parameter specifies must be created with the GENERIC_READ, GENERIC_WRITE, and GENERIC_EXECUTE access rights. Windows Server 2003 and Windows XP: This value is not available until Windows XP with SP2 and Windows Server 2003 with SP1. Windows 2000: This value is not supported. PAGE_EXECUTE_WRITECOPYAllows views to be mapped for read-only, copy-on-write, or execute access. This value is equivalent to PAGE_EXECUTE_READ. The file handle that the hFile parameter specifies must be created with the GENERIC_READ and GENERIC_EXECUTE access rights. Windows Server 2003 and Windows XP/2000: This value is not supported. Windows Vista: This value is not available until Windows Vista with SP1. PAGE_READONLYAllows views to be mapped for read-only or copy-on-write access. An attempt to write to a specific region results in an access violation. The file handle that the hFile parameter specifies must be created with the GENERIC_READ access right. PAGE_READWRITEAllows views to be mapped for read-only, copy-on-write, or read/write access. The file handle that the hFile parameter specifies must be created with the GENERIC_READ and GENERIC_WRITE access rights. PAGE_WRITECOPYAllows views to be mapped for read-only or copy-on-write access. This value is equivalent to PAGE_READONLY. The file handle that the hFile parameter specifies must be created with the GENERIC_READ access right. An application can specify one or more of the following attributes for the file mapping object by combining them with one of the preceding page protection values. ValueMeaning SEC_COMMITIf the file mapping object is backed by the operating system paging file (the hfile parameter is INVALID_HANDLE_VALUE), specifies that when a view of the file is mapped into a process address space, the entire range of pages is committed rather than reserved. The system must have enough committable pages to hold the entire mapping. Otherwise, CreateFileMapping fails. This attribute has no effect for file mapping objects that are backed by executable image files or data files (the hfile parameter is a handle to a file). SEC_COMMIT cannot be combined with SEC_RESERVE. If no attribute is specified, SEC_COMMIT is assumed. SEC_IMAGESpecifies that the file that the hFile parameter specifies is an executable image file. Because the mapping information and file protection are taken from the image file, no other attributes are valid with SEC_IMAGE. SEC_LARGE_PAGESEnables large pages to be used for file mapping objects that are backed by the operating system paging file (the hfile parameter is INVALID_HANDLE_VALUE). This attribute is not supported for file mapping objects that are backed by executable image files or data files (the hFile parameter is a handle to an executable image or data file). The maximum size of the file mapping object must be a multiple of the minimum size of a large page returned by the GetLargePageMinimum function. If it is not, CreateFileMapping fails. When mapping a view of a file mapping object created with SEC_LARGE_PAGES, the base address and view size must also be multiples of the minimum large page size. SEC_LARGE_PAGES requires the SeLockMemoryPrivilege privilege to be enabled in the caller's token. If SEC_LARGE_PAGES is specified, SEC_COMMIT must also be specified. Windows Server 2003: This value is not supported until Windows Server 2003 with SP1. Windows XP/2000: This value is not supported. SEC_NOCACHESets all pages to be non-cachable. Applications should not use this attribute except when explicitly required for a device. Using the interlocked functions with memory that is mapped with SEC_NOCACHE can result in an EXCEPTION_ILLEGAL_INSTRUCTION exception. SEC_NOCACHE requires either the SEC_RESERVE or SEC_COMMIT attribute to be set. SEC_RESERVEIf the file mapping object is backed by the operating system paging file (the hfile parameter is INVALID_HANDLE_VALUE), specifies that when a view of the file is mapped into a process address space, the entire range of pages is reserved for later use by the process rather than committed. Reserved pages can be committed in subsequent calls to the VirtualAlloc function. After the pages are committed, they cannot be freed or decommitted with the VirtualFree function. This attribute has no effect for file mapping objects that are backed by executable image files or data files (the hfile parameter is a handle to a file). SEC_RESERVE cannot be combined with SEC_COMMIT. SEC_WRITECOMBINESets all pages to be write-combined. Applications should not use this attribute except when explicitly required for a device. Using the interlocked functions with memory that is mapped with SEC_WRITECOMBINE can result in an EXCEPTION_ILLEGAL_INSTRUCTION exception. SEC_WRITECOMBINE requires either the SEC_RESERVE or SEC_COMMIT attribute to be set. Windows Server 2003 and Windows XP/2000: This flag is not supported until Windows Vista. dwMaximumSizeHigh [in] The high-order DWORD of the maximum size of the file mapping object. dwMaximumSizeLow [in] The low-order DWORD of the maximum size of the file mapping object. If this parameter and dwMaximumSizeHigh are 0 (zero), the maximum size of the file mapping object is equal to the current size of the file that hFile identifies. An attempt to map a file with a length of 0 (zero) fails with an error code of ERROR_FILE_INVALID. Applications should test for files with a length of 0 (zero) and reject those files. lpName [in, optional] The name of the file mapping object. If this parameter matches the name of an existing mapping object, the function requests access to the object with the protection that flProtect specifies. If this parameter is NULL, the file mapping object is created without a name. If lpName matches the name of an existing event, semaphore, mutex, waitable timer, or job object, the function fails, and the GetLastError function returns ERROR_INVALID_HANDLE. This occurs because these objects share the same namespace. Terminal Services: The name can have a "Global\\" or "Local\\" prefix to explicitly create the object in the global or session namespace. The remainder of the name can contain any character except the backslash character (\\). Creating a file mapping object in the global namespace from a session other than session zero requires the SeCreateGlobalPrivilege privilege. For more information, see Kernel Object Namespaces . Windows XP: Fast user switching is implemented by using Terminal Services sessions. The first user to log on uses session 0 (zero), the next user to log on uses session 1 (one), and so on. Kernel object names must follow the guidelines that are outlined for Terminal Services so that applications can support multiple users. Windows 2000: If Terminal Services is not running, the "Global\\" and "Local\\" prefixes are ignored. The remainder of the name can contain any character except the backslash character. Return Value If the function succeeds, the return value is a handle to the newly created file mapping object. If the object exists before the function call, the function returns a handle to the existing object (with its current size, not the specified size), and GetLastError returns ERROR_ALREADY_EXISTS. If the function fails, the return value is NULL. To get extended error information, call GetLastError. Remarks After a file mapping object is created, the size of the file must not exceed the size of the file mapping object; if it does, not all of the file contents are available for sharing. If an application specifies a size for the file mapping object that is larger than the size of the actual named file on disk and if the page protection allows write access (that is, the flProtect parameter specifies PAGE_READWRITE or PAGE_EXECUTE_READWRITE), then the file on disk is increased to match the specified size of the file mapping object. If the file is extended, the contents of the file between the old end of the file and the new end of the file are not guaranteed to be zero; the behavior is defined by the file system. If the file on disk cannot be increased, CreateFileMapping fails and GetLastError returns ERROR_DISK_FULL. The initial contents of the pages in a file mapping object backed by the operating system paging file are 0 (zero). The handle that CreateFileMapping returns has full access to a new file mapping object, and can be used with any function that requires a handle to a file mapping object. Multiple processes can share a view of the same file by either using a single shared file mapping object or creating separate file mapping objects backed by the same file. A single file mapping object can be shared by multiple processes through inheriting the handle at process creation, duplicating the handle, or opening the file mapping object by name. For more information, see the CreateProcess , DuplicateHandle and OpenFileMapping functions. Creating a file mapping object does not actually map the view into a process address space. The MapViewOfFile and MapViewOfFileEx functions map a view of a file into a process address space. With one important exception, file views derived from any file mapping object that is backed by the same file are coherent or identical at a specific time. Coherency is guaranteed for views within a process and for views that are mapped by different processes. The exception is related to remote files. Although CreateFileMapping works with remote files, it does not keep them coherent. For example, if two computers both map a file as writable, and both change the same page, each computer only sees its own writes to the page. When the data gets updated on the disk, it is not merged. A mapped file and a file that is accessed by using the input and output (I/O) functions ( ReadFile and WriteFile ) are not necessarily coherent. Mapped views of a file mapping object maintain internal references to the object, and a file mapping object does not close until all references to it are released. Therefore, to fully close a file mapping object, an application must unmap all mapped views of the file mapping object by calling UnmapViewOfFile and close the file mapping object handle by calling CloseHandle . These functions can be called in any order. Creating a file mapping object in the global namespace from a session other than session zero requires the SeCreateGlobalPrivilege privilege. Note that this privilege check is limited to the creation of file mapping objects and does not apply to opening existing ones. For example, if a service or the system creates a file mapping object in the global namespace, any process running in any session can access that file mapping object provided that the caller has the required access rights. Windows XP/2000: The requirement described in the previous paragraph was introduced with Windows Server 2003, Windows XP with SP2 and Windows 2000 Server with Service Pack 4 (SP4) Use structured exception handling to protect any code that writes to or reads from a file view. For more information, see Reading and Writing From a File View . To have a mapping with executable permissions, an application must call CreateFileMapping with either PAGE_EXECUTE_READWRITE or PAGE_EXECUTE_READ, and then call MapViewOfFile with FILE_MAP_EXECUTE | FILE_MAP_WRITE or FILE_MAP_EXECUTE | FILE_MAP_READ. Examples For an example, see Creating Named Shared Memory or Creating a File Mapping Using Large Pages . Requirements Minimum supported clientWindows 2000 Professional Minimum supported serverWindows 2000 Server HeaderWinbase.h (include Windows.h) LibraryKernel32.lib DLLKernel32.dll Unicode and ANSI namesCreateFileMappingW (Unicode) and CreateFileMappingA (ANSI) See Also CloseHandle CreateFileMappingNuma Creating a File Mapping Object DuplicateHandle File Mapping Functions MapViewOfFile MapViewOfFileEx OpenFileMapping ReadFile SECURITY_ATTRIBUTES UnmapViewOfFile VirtualAlloc WriteFile Send comments about this topic to Microsoft Build date: 8/27/2009 ＝＝原始网址＝＝http://msdn.microsoft.com/en-us/library/aa366537(VS.85).aspx\n |
| 随便看 |
|
windows api函数参考手册包含2258条windows api函数文档，详细介绍nodejs、java、rust调用windows api的方法技巧，是学习windows api编程的入门中文文档。