Hi Andreas,
On Sat, 1 Nov 2014 18:01:07 +0100, Andreas Rohner wrote:
> If some of the pages between start and end are dirty, then
> filemap_write_and_wait_range() calls nilfs_writepages() with WB_SYNC_ALL
> set in the writeback_control structure. This initiates the construction
> of a dsync segment via nilfs_construct_dsync_segment(). The problem is,
> that the construction of a dsync segment doesnt't remove the inode from
> die i_dirty list and doesn't clear the NILFS_I_DIRTY flag. So
> nilfs_inode_dirty() still returns true after
> nilfs_construct_dsync_segment() succeded. This leads to an
> unnecessary second call to nilfs_construct_dsync_segment() in
> nilfs_sync_file() if datasync is true.
>
> This patch simply removes the second invokation of
> nilfs_construct_dsync_segment().
>
> Signed-off-by: Andreas Rohner <[email protected]>
Thank you for posting this patch.
This optimization looks to become possible by the commit 02c24a821
"fs: push i_mutex and filemap_write_and_wait down into ->fsync()
handlers". I haven't noticed that the change makes it possible to
simplify nilfs_sync_file() like this.
One my simple question is why you removed the call to
nilfs_construct_dsync_segment() instead of
filemap_write_and_wait_range().
If the datasync flag is false, nilfs_sync_file() first calls
nilfs_construct_dsync_segment() via
filemap_write_and_wait_range()
__filemap_fdatawrite_range(,, WB_SYNC_ALL)
do_writepages()
nilfs_writepages()
nilfs_construct_dsync_segment()
and then calls nilfs_construct_segment().
Since each call to nilfs_construct_segment() or
nilfs_construct_dsync_segment() implies an IO completion wait, it
seems that this doubles the latency of fsync().
Do you really need to call filemap_write_and_wait_range() in
nilfs_sync_file() ?
Regards,
Ryusuke Konishi
> ---
> fs/nilfs2/file.c | 10 +++-------
> 1 file changed, 3 insertions(+), 7 deletions(-)
>
> diff --git a/fs/nilfs2/file.c b/fs/nilfs2/file.c
> index e9e3325..b12e0ab 100644
> --- a/fs/nilfs2/file.c
> +++ b/fs/nilfs2/file.c
> @@ -46,13 +46,9 @@ int nilfs_sync_file(struct file *file, loff_t start,
> loff_t end, int datasync)
> return err;
> mutex_lock(&inode->i_mutex);
>
> - if (nilfs_inode_dirty(inode)) {
> - if (datasync)
> - err = nilfs_construct_dsync_segment(inode->i_sb, inode,
> - 0, LLONG_MAX);
> - else
> - err = nilfs_construct_segment(inode->i_sb);
> - }
> + if (!datasync && nilfs_inode_dirty(inode))
> + err = nilfs_construct_segment(inode->i_sb);
> +
> mutex_unlock(&inode->i_mutex);
>
> nilfs = inode->i_sb->s_fs_info;
> --
> 2.1.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
