diff options
| author | Darrick J. Wong <[email protected]> | 2016-10-11 13:51:11 -0700 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2016-10-11 15:06:30 -0700 |
| commit | 25f4c41415e513f0e9fb1f3fce2ce98fcba8d263 (patch) | |
| tree | 5a81f8273c46ec83d30c6bddb6e1e3a0e6941024 /tools/perf/scripts/python/bin | |
| parent | 28b2be203e5a09de566d6f7e21183f861e36f07e (diff) | |
block: implement (some of) fallocate for block devices
After much discussion, it seems that the fallocate feature flag
FALLOC_FL_ZERO_RANGE maps nicely to SCSI WRITE SAME; and the feature
FALLOC_FL_PUNCH_HOLE maps nicely to the devices that have been whitelisted
for zeroing SCSI UNMAP. Punch still requires that FALLOC_FL_KEEP_SIZE is
set. A length that goes past the end of the device will be clamped to the
device size if KEEP_SIZE is set; or will return -EINVAL if not. Both
start and length must be aligned to the device's logical block size.
Since the semantics of fallocate are fairly well established already, wire
up the two pieces. The other fallocate variants (collapse range, insert
range, and allocate blocks) are not supported.
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Darrick J. Wong <[email protected]>
Reviewed-by: Hannes Reinecke <[email protected]>
Reviewed-by: Bart Van Assche <[email protected]>
Cc: Theodore Ts'o <[email protected]>
Cc: Martin K. Petersen <[email protected]>
Cc: Mike Snitzer <[email protected]> # tweaked header
Cc: Brian Foster <[email protected]>
Cc: Christoph Hellwig <[email protected]>
Cc: Hannes Reinecke <[email protected]>
Cc: Jens Axboe <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions