diff options
author | Lukas Czerner <lczerner@redhat.com> | 2010-10-27 21:30:11 -0400 |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2010-10-27 21:30:11 -0400 |
commit | 367a51a339020ba4d9edb0ce0f21d65bd50b00c9 (patch) | |
tree | 696cbb5ca3108cd0cf8a7c3f494947cc9a4179c7 /fs/ext4/super.c | |
parent | 77ca6cdf0ab8a42f481ec997911bc89e79138723 (diff) | |
download | linux-stable-367a51a339020ba4d9edb0ce0f21d65bd50b00c9.tar.gz linux-stable-367a51a339020ba4d9edb0ce0f21d65bd50b00c9.tar.bz2 linux-stable-367a51a339020ba4d9edb0ce0f21d65bd50b00c9.zip |
fs: Add FITRIM ioctl
Adds an filesystem independent ioctl to allow implementation of file
system batched discard support. I takes fstrim_range structure as an
argument. fstrim_range is definec in the include/fs.h and its
definition is as follows.
struct fstrim_range {
start;
len;
minlen;
}
start - first Byte to trim
len - number of Bytes to trim from start
minlen - minimum extent length to trim, free extents shorter than this
number of Bytes will be ignored. This will be rounded up to fs
block size.
It is also possible to specify NULL as an argument. In this case the
arguments will set itself as follows:
start = 0;
len = ULLONG_MAX;
minlen = 0;
So it will trim the whole file system at one run.
After the FITRIM is done, the number of actually discarded Bytes is stored
in fstrim_range.len to give the user better insight on how much storage
space has been really released for wear-leveling.
Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Reviewed-by: Dmitry Monakhov <dmonakhov@openvz.org>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'fs/ext4/super.c')
0 files changed, 0 insertions, 0 deletions