Chris Mason <[email protected]> writes:
> Ok, I thought you were asking about the code that called filemap_fdatawrite,
> which does wait. filemap_flush is used on the underlying block device. In
> the case of a page that is already under IO, the io is not cancelled but
> allowed to continue.
>
> This is the desired result. When you're doing a number of operations in
> sequence, each operation will start io on the block device. If they used
> filemap_fdatawrite instead of filemap_flush, they would end up being
> synchronous.
Of course, I know. Let's return to beginning of this thread, do you have
any plan to address it?
--
OGAWA Hirofumi <[email protected]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
