You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Jan Kara 2c948b3f86 udf: Avoid IO in udf_clear_inode ... It is not very good to do IO in udf_clear_inode. First, VFS does not really expect inode to become dirty there and thus we have to write it ourselves, second, memory reclaim gets blocked waiting for IO when it does not really expect it, third, the IO pattern (e.g. on umount) resulting from writes in udf_clear_inode is bad and it slows down writing a lot. The reason why UDF needed to do IO in udf_clear_inode is that UDF standard mandates extent length to exactly match inode size. But when we allocate extents to a file or directory, we don't really know what exactly the final file size will be and thus temporarily set it to block boundary and later truncate it to exact length in udf_clear_inode. Now, this is changed to truncate to final file size in udf_release_file for regular files. For directories and symlinks, we do the truncation at the moment when learn what the final file size will be. Signed-off-by: Jan Kara <jack@suse.cz>		15 years ago
..
Kconfig	…
Makefile	…
balloc.c	…
dir.c	…
directory.c	…
ecma_167.h	…
file.c	udf: Avoid IO in udf_clear_inode	15 years ago
ialloc.c	…
inode.c	udf: Avoid IO in udf_clear_inode	15 years ago
lowlevel.c	…
misc.c	…
namei.c	udf: Avoid IO in udf_clear_inode	15 years ago
osta_udf.h	…
partition.c	…
super.c	…
symlink.c	…
truncate.c	…
udf_i.h	…
udf_sb.h	…
udfdecl.h	…
udfend.h	…
udftime.c	…
unicode.c	…