Penguin

Differences between current version and predecessor to the previous major change of msync(2).

Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History

Newer page: version 2 Last edited on Saturday, March 15, 2003 1:38:24 am by PerryLorier
Older page: version 1 Last edited on Tuesday, June 4, 2002 12:23:43 am by perry Revert
@@ -1,79 +1,31 @@
-MSYNC  
-!!!MSYNC  
-NAME  
-SYNOPSIS  
-DESCRIPTION  
-RETURN VALUE  
-ERRORS  
-CONFORMING TO  
-SEE ALSO  
-----  
 !!NAME 
+msync - synchronize a file with a memory map  
  
-  
-msync - synchronize a file with a memory map  
 !!SYNOPSIS 
+ __#include <unistd.h>__  
+ __#include <sys/mman.h>__  
  
+ __#ifdef _POSIX_MAPPED_FILES__  
+ __#ifdef _POSIX_SYNCHRONIZED_IO__  
  
-__#include __  
-#include __ 
+ __int msync(const void * __''start''__, size_t__ ''length''__, int__ ''flags''__); __ 
  
-  
- __#ifdef _POSIX _MAPPED_FILES  
-#ifdef _POSIX _SYNCHRONIZED_IO__  
-  
-  
-__int msync(const void *__''start''__, size_t__  
-''length''__, int__ ''flags''__);__  
-  
-  
-__#endif  
- #endif__ 
+ __#endif __  
+ __#endif__ 
 !!DESCRIPTION 
+__msync__ flushes changes made to the in-core copy of a file that was mapped into memory using mmap(2) back to disk. Without use of this call there is no guarantee that  
+changes are written back before munmap(2) is called. To be more precise, the part of the file that corresponds to the memory area starting at ''start'' and having length  
+''length'' is updated. The ''flags'' argument may have the bits MS_ASYNC, MS_SYNC and MS_INVALIDATE set, but not both MS_ASYNC and MS_SYNC. MS_ASYNC specifies that an update be scheduled, but the call returns immediately. MS_SYNC asks for an update and waits for it to complete. MS_INVALIDATE asks to invalidate other mappings of the same file (so that they can be updated with the fresh values just written).  
  
-  
-__msync__ flushes changes made to the in-core copy of a  
-file that was mapped into memory using mmap(2) back  
-to disk. Without use of this call there is no guarantee that  
-changes are written back before munmap(2) is called.  
-To be more precise, the part of the file that corresponds to  
-the memory area starting at ''start'' and having length  
-''length'' is updated. The ''flags'' argument may have  
-the bits MS_ASYNC, MS_SYNC and MS_INVALIDATE set, but not  
-both MS_ASYNC and MS_SYNC. MS_ASYNC specifies that an update  
-be scheduled, but the call returns immediately. MS_SYNC asks  
-for an update and waits for it to complete. MS_INVALIDATE  
-asks to invalidate other mappings of the same file (so that  
-they can be updated with the fresh values just  
-written).  
 !!RETURN VALUE 
+On success, zero is returned. On error, -1 is returned, and ''errno'' is set appropriately.  
  
-  
-On success, zero is returned. On error, -1 is returned, and  
-''errno'' is set appropriately.  
 !!ERRORS 
+;[EINVAL]: ''start'' is not a multiple of PAGESIZE, or any bit other than MS_ASYNC | MS_INVALIDATE | MS_SYNC is set in ''flags.''  
+;[EFAULT]: The indicated memory (or part of it) was not mapped.  
  
-  
-__EINVAL__  
-  
-  
-''start'' is not a multiple of PAGESIZE, or any bit other  
-than MS_ASYNC | MS_INVALIDATE | MS_SYNC is set in  
-''flags.''  
-  
-  
-__EFAULT__  
-  
-  
-The indicated memory (or part of it) was not  
-mapped.  
 !!CONFORMING TO 
+POSIX.1b (formerly POSIX.4)  
  
-  
-POSIX.1b (formerly POSIX.4)  
 !!SEE ALSO 
-  
-  
- mmap(2), B.O. Gallmeister, POSIX.4, O'Reilly, pp.  
- 128-129 and 389-391.  
-----  
+mmap(2), B.O. Gallmeister, POSIX.4, O'Reilly, pp. 128-129 and 389-391. 
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.