<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="Memory-mapped file - Page 13 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Memory-mapped_file&amp;p=12">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Memory-mapped_file&amp;p=14">3.Next</a>
</p>
<p>modern <a href="page.php?w=NVM_Express">NVM Express</a> SSDs, are capable of making the overhead a real concern.</p>

<p>I/O errors on the underlying file (e.g. its removable drive is unplugged or optical media is ejected, disk full when writing, etc.) while accessing its mapped memory are reported to the application as the SIGSEGV/SIGBUS signals on POSIX, and the EXECUTE_IN_PAGE_ERROR structured exception on Windows. All code accessing mapped memory must be prepared to handle these errors, which don't normally occur when accessing memory.</p>

<p>Only</p><p>
<a accesskey="1" href="page.php?w=Memory-mapped_file&amp;p=12">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Memory-mapped_file&amp;p=14">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
