[PATCH] Kill PF_SYNCWRITE flag
A process flag to indicate whether we are doing sync io is incredibly ugly. It also causes performance problems when one does a lot of async io and then proceeds to sync it. Part of the io will go out as async, and the other part as sync. This causes a disconnect between the previously submitted io and the synced io. For io schedulers such as CFQ, this will cause us lost merges and suboptimal behaviour in scheduling. Remove PF_SYNCWRITE completely from the fsync/msync paths, and let the O_DIRECT path just directly indicate that the writes are sync by using WRITE_SYNC instead. Signed-off-by: Jens Axboe <axboe@suse.de>
This commit is contained in:
@@ -1906,7 +1906,6 @@ static int fsync_sub(struct lun *curlun)
|
||||
|
||||
inode = filp->f_dentry->d_inode;
|
||||
mutex_lock(&inode->i_mutex);
|
||||
current->flags |= PF_SYNCWRITE;
|
||||
rc = filemap_fdatawrite(inode->i_mapping);
|
||||
err = filp->f_op->fsync(filp, filp->f_dentry, 1);
|
||||
if (!rc)
|
||||
@@ -1914,7 +1913,6 @@ static int fsync_sub(struct lun *curlun)
|
||||
err = filemap_fdatawait(inode->i_mapping);
|
||||
if (!rc)
|
||||
rc = err;
|
||||
current->flags &= ~PF_SYNCWRITE;
|
||||
mutex_unlock(&inode->i_mutex);
|
||||
VLDBG(curlun, "fdatasync -> %d\n", rc);
|
||||
return rc;
|
||||
|
Reference in New Issue
Block a user