History

block: enable dax for raw block devices

If an application wants exclusive access to all of the persistent memory provided by an NVDIMM namespace it can use this raw-block-dax facility to forgo establishing a filesystem. This capability is targeted primarily to hypervisors wanting to provision persistent memory for guests. It can be disabled / enabled dynamically via the new BLKDAXSET ioctl.

Dan Williams committed 10 years ago

Commit 5a023cd1 parent 4ebb16c4 files · +169 −8Browse files

Showing the changes to include/uapi (1 of 4 files). Show all

Unified · Split

include/uapi/linux/fs.h+2−0
@@ -152,6 +152,8 @@ struct inodes_stat_t { · 151 unmodified lines
152#define BLKSECDISCARD _IO(0x12,125)152#define BLKSECDISCARD _IO(0x12,125)
153#define BLKROTATIONAL _IO(0x12,126)153#define BLKROTATIONAL _IO(0x12,126)
154#define BLKZEROOUT _IO(0x12,127)154#define BLKZEROOUT _IO(0x12,127)
155#define BLKDAXSET _IO(0x12,128)
156#define BLKDAXGET _IO(0x12,129)
155 157
156#define BMAP_IOCTL 1 /* obsolete - kept for compatibility */158#define BMAP_IOCTL 1 /* obsolete - kept for compatibility */
157#define FIBMAP _IO(0x00,1) /* bmap access */159#define FIBMAP _IO(0x00,1) /* bmap access */

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t