summaryrefslogtreecommitdiffstats
path: root/fs/direct-io.c
diff options
context:
space:
mode:
authorJosef Bacik <jbacik@fb.com>2014-01-15 13:34:13 -0500
committerChris Mason <clm@fb.com>2014-01-28 13:20:25 -0800
commit5039eddc19aee8c894191c24f2dde4e645ca1bbb (patch)
tree2fd4f5447094d374a1645ee8d4dfaf8649c97f95 /fs/direct-io.c
parent63541927c8d11d2686778b1e8ec71c14b4fd53e4 (diff)
downloadop-kernel-dev-5039eddc19aee8c894191c24f2dde4e645ca1bbb.zip
op-kernel-dev-5039eddc19aee8c894191c24f2dde4e645ca1bbb.tar.gz
Btrfs: make fsync latency less sucky
Looking into some performance related issues with large amounts of metadata revealed that we can have some pretty huge swings in fsync() performance. If we have a lot of delayed refs backed up (as you will tend to do with lots of metadata) fsync() will wander off and try to run some of those delayed refs which can result in reading from disk and such. Since the actual act of fsync() doesn't create any delayed refs there is no need to make it throttle on delayed ref stuff, that will be handled by other people. With this patch we get much smoother fsync performance with large amounts of metadata. Thanks, Signed-off-by: Josef Bacik <jbacik@fb.com> Signed-off-by: Chris Mason <clm@fb.com>
Diffstat (limited to 'fs/direct-io.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud