From: Hillf Danton <hdanton@sina.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: use rwlock instead of rwsem for journal
Date: Thu, 22 Jul 2021 11:06:57 +0800 [thread overview]
Message-ID: <20210722030657.1155-1-hdanton@sina.com> (raw)
In-Reply-To: <20210722014149.525166-1-jaegeuk@kernel.org>
On Wed, 21 Jul 2021 18:41:49 -0700 Jaegeuk Kim wrote:
>
>This tries to fix priority inversion in the below condition resulting in
>long checkpoint delay.
If you are right and the patch makes real sense, feel free to specify a bit
more on the priority inversion you are trying to fix, and how the fix helps
shorten the checkpoint delay. And test data is welcome.
>
>f2fs_get_node_info()
> - nat_tree_lock
> -> sleep in journal_rwsem
> checkpoint
> - waiting for nat_tree_lock
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2021-07-22 3:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 1:41 [PATCH] f2fs: use rwlock instead of rwsem for journal Jaegeuk Kim
2021-07-22 1:41 ` [f2fs-dev] " Jaegeuk Kim
2021-07-22 3:06 ` Hillf Danton [this message]
2021-07-22 13:41 ` Chao Yu
2021-07-22 13:41 ` Chao Yu
2021-07-22 17:44 ` [PATCH v2] f2fs: don't sleep while grabing nat_tree_lock Jaegeuk Kim
2021-07-22 17:44 ` [f2fs-dev] " Jaegeuk Kim
2021-07-23 0:39 ` Chao Yu
2021-07-23 0:39 ` Chao Yu
2021-07-23 2:35 ` [PATCH v3] " Jaegeuk Kim
2021-07-23 2:35 ` [f2fs-dev] " Jaegeuk Kim
2021-07-23 2:41 ` Chao Yu
2021-07-23 2:41 ` Chao Yu
2021-07-23 4:27 ` [f2fs-dev] [PATCH v4] " Jaegeuk Kim
2021-07-23 4:27 ` Jaegeuk Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210722030657.1155-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.