summaryrefslogtreecommitdiffstats
path: root/fs/coda
diff options
context:
space:
mode:
authorXiubo Li <xiubli@redhat.com>2021-07-05 09:22:57 +0800
committerIlya Dryomov <idryomov@gmail.com>2021-09-02 22:49:16 +0200
commite1a4541ec0b951685a49d1f72d183681e6433a45 (patch)
tree35a970d5aabd17a572dfe39566a6a761bf29ffe6 /fs/coda
parentd095559ce4100f0c02aea229705230deac329c97 (diff)
downloadlinux-e1a4541ec0b951685a49d1f72d183681e6433a45.tar.bz2
ceph: flush the mdlog before waiting on unsafe reqs
For the client requests who will have unsafe and safe replies from MDS daemons, in the MDS side the MDS daemons won't flush the mdlog (journal log) immediatelly, because they think it's unnecessary. That's true for most cases but not all, likes the fsync request. The fsync will wait until all the unsafe replied requests to be safely replied. Normally if there have multiple threads or clients are running, the whole mdlog in MDS daemons could be flushed in time if any request will trigger the mdlog submit thread. So usually we won't experience the normal operations will stuck for a long time. But in case there has only one client with only thread is running, the stuck phenomenon maybe obvious and the worst case it must wait at most 5 seconds to wait the mdlog to be flushed by the MDS's tick thread periodically. This patch will trigger to flush the mdlog in the relevant and auth MDSes to which the in-flight requests are sent just before waiting the unsafe requests to finish. Signed-off-by: Xiubo Li <xiubli@redhat.com> Reviewed-by: Jeff Layton <jlayton@kernel.org> Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
Diffstat (limited to 'fs/coda')
0 files changed, 0 insertions, 0 deletions