From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: avoid migratepage for atomic written page
Date: Thu, 6 Jul 2017 21:38:34 +0800 [thread overview]
Message-ID: <e95a37f3-5403-20c8-606f-ed1a55fa67b7@kernel.org> (raw)
In-Reply-To: <20170703230820.63929-1-jaegeuk@kernel.org>
Hi Jaegeuk,
On 2017/7/4 7:08, Jaegeuk Kim wrote:
> In order to avoid lock contention for atomic written pages, we'd better give
> EAGAIN in f2fs_migrate_page. We expect it will be released soon as transaction
> commits.
Hmm.. if atomic write is triggered intensively, there is little change to
migrate fragmented page.
How about detecting migrate mode here, for MIGRATE_SYNC case, let it moving
the page; for MIGRATE_ASYNC/MIGRATE_SYNC_LIGHT case, the migration priority
is lower, we can return EAGAIN.
Thanks,
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
> fs/f2fs/data.c | 35 ++++++++++-------------------------
> 1 file changed, 10 insertions(+), 25 deletions(-)
>
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index d58b81213a86..1458e3a6d630 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -2197,41 +2197,26 @@ static sector_t f2fs_bmap(struct address_space *mapping, sector_t block)
> int f2fs_migrate_page(struct address_space *mapping,
> struct page *newpage, struct page *page, enum migrate_mode mode)
> {
> - int rc, extra_count;
> - struct f2fs_inode_info *fi = F2FS_I(mapping->host);
> - bool atomic_written = IS_ATOMIC_WRITTEN_PAGE(page);
> + int rc;
>
> - BUG_ON(PageWriteback(page));
> -
> - /* migrating an atomic written page is safe with the inmem_lock hold */
> - if (atomic_written && !mutex_trylock(&fi->inmem_lock))
> + /*
> + * We'd better return EAGAIN for atomic pages, which will be committed
> + * sooner or later. Don't botter transactions with inmem_lock.
> + */
> + if (IS_ATOMIC_WRITTEN_PAGE(page))
> return -EAGAIN;
>
> + BUG_ON(PageWriteback(page)); /* Writeback must be complete */
> +
> /*
> * A reference is expected if PagePrivate set when move mapping,
> * however F2FS breaks this for maintaining dirty page counts when
> * truncating pages. So here adjusting the 'extra_count' make it work.
> */
> - extra_count = (atomic_written ? 1 : 0) - page_has_private(page);
> rc = migrate_page_move_mapping(mapping, newpage,
> - page, NULL, mode, extra_count);
> - if (rc != MIGRATEPAGE_SUCCESS) {
> - if (atomic_written)
> - mutex_unlock(&fi->inmem_lock);
> + page, NULL, mode, (page_has_private(page) ? -1 : 0));
> + if (rc != MIGRATEPAGE_SUCCESS)
> return rc;
> - }
> -
> - if (atomic_written) {
> - struct inmem_pages *cur;
> - list_for_each_entry(cur, &fi->inmem_pages, list)
> - if (cur->page == page) {
> - cur->page = newpage;
> - break;
> - }
> - mutex_unlock(&fi->inmem_lock);
> - put_page(page);
> - get_page(newpage);
> - }
>
> if (PagePrivate(page))
> SetPagePrivate(newpage);
>
next prev parent reply other threads:[~2017-07-06 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 23:08 [PATCH] f2fs: avoid migratepage for atomic written page Jaegeuk Kim
2017-07-06 13:38 ` Chao Yu [this message]
2017-07-06 21:49 ` [PATCH v2] f2fs: relax " Jaegeuk Kim
2017-07-06 23:57 ` [f2fs-dev] " Chao Yu
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=e95a37f3-5403-20c8-606f-ed1a55fa67b7@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).