History

vfs: add a FALLOC_FL_UNSHARE mode to fallocate to unshare a range of blocks

Add a new fallocate mode flag that explicitly unshares blocks on filesystems that support such features. The new flag can only be used with an allocate-mode fallocate call.

Darrick J. Wong committed 10 years ago

Commit 71be6b41 parent 0a6eab83 files · +25 −1Browse files

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

Unified · Split

include/uapi/linux/falloc.h+18−0
@@ -58,4 +58,22 @@ · 57 unmodified lines
5858 */
5959 #define FALLOC_FL_INSERT_RANGE 0x20
6060
61+/*
62+ * FALLOC_FL_UNSHARE_RANGE is used to unshare shared blocks within the
63+ * file size without overwriting any existing data. The purpose of this
64+ * call is to preemptively reallocate any blocks that are subject to
65+ * copy-on-write.
66+ *
67+ * Different filesystems may implement different limitations on the
68+ * granularity of the operation. Most will limit operations to filesystem
69+ * block size boundaries, but this boundary may be larger or smaller
70+ * depending on the filesystem and/or the configuration of the filesystem
71+ * or file.
72+ *
73+ * This flag can only be used with allocate-mode fallocate, which is
74+ * to say that it cannot be used with the punch, zero, collapse, or
75+ * insert range modes.
76+ */
77+#define FALLOC_FL_UNSHARE_RANGE 0x40
78+
6179 #endif /* _UAPI_FALLOC_H_ */

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