From WikiChip
Editing snia/direct access

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

This page supports semantic in-text annotations (e.g. "[[Is specified as::World Heritage Site]]") to build structured and queryable content provided by Semantic MediaWiki. For a comprehensive description on how to use annotations or the #ask parser function, please have a look at the getting started, in-text annotation, or inline queries help pages.

Latest revision Your text
Line 1: Line 1:
 
{{title|Direct Access (DAX) - SNIA}}
 
{{title|Direct Access (DAX) - SNIA}}
'''Direct Access''' ('''DAX''') is a mechanism defined by [[SNIA]] as part of the {{snia|NVM Programming Model}} that provides byte-addressable loads and stores when working with a [[persistent memory-aware file system]] through direct [[MMU]] mappings.
+
'''Direct Access''' ('''DAX''') is a mechanism defined by [[SNIA]] as part of the {{snia|NVM Programming Model}} that provides byte-addressable loads and stores when working with a [[persistent memory-aware file system]].
 
 
== Overview ==
 
The traditional file I/O APIs usually provide a mechanism called [[memory-mapped file]] whereby a portion of a file is mapped directly onto the [[virtual memory]] of an application with a byte-for-byte correlation between the two. An application can then use standard pointers to operate on the data through normal loads and stores in a byte-addressable fashion. Although, from the software perspective, the operations are done on single bytes, in reality [[paging]] is involved as traditional [[block storage]] I/O must be done in blocks. On a byte access, the operating system must read a full block (typically around 4 KiB or so) from the storage device into memory. Likewise, on a store, the operating system must write out the entire block back to the storage device.
 
 
 
The direct access (DAX) mechanism of the [[persistent memory-aware file system]] allows the kernel to set up a direct load-store access to the persistent medium through direct [[MMU]] mappings, instead of the paged-access found in traditional block storage. In other words, in addition for traditional block-level support, the {{snia|NVM Programming Model}} allows for direct byte-level access to the non-volatile media.
 
 
 
== See also ==
 
* {{snia|NVM Programming Model}}
 

Please note that all contributions to WikiChip may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see WikiChip:Copyrights for details). Do not submit copyrighted work without permission!

Cancel | Editing help (opens in new window)