title: mmap, msync and linux process termination
body: <p>I want to use mmap to implement persistence of certain portions of program state in a C program running under Linux by associating a fixed-size struct with a well known file name using mmap() with the MAP_SHARED flag set.  For performance reasons, I would prefer not to call msync() at all, and no other programs will be accessing this file.  When my program terminates and is restarted, it will map the same file again and do some processing on it to recover the state that it was in before the termination.  My question is this: if I never call msync() on the file descriptor, will the kernel guarantee that all updates to the memory will get written to disk and be subsequently recoverable even if my process is terminated with SIGKILL?  Also, will there be general system overhead from the kernel periodically writing the pages to disk even if my program never calls msync()?</p>
  
  <p><strong>EDIT:</strong> I've settled the problem of whether the data is written, but I'm still not sure about whether this will cause some unexpected system loading over trying to handle this problem with open()/write()/fsync() and taking the risk that some data might be lost if the process gets hit by KILL/SEGV/ABRT/etc.  Added a 'linux-kernel' tag in hopes that some knowledgeable person might chime in.</p>