All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Fengnan Chang <changfengnan@vivo.com>, jaegeuk@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2 2/3] f2fs: use onstack pages instead of pvec
Date: Mon, 11 Jul 2022 17:46:42 +0800	[thread overview]
Message-ID: <04cc6525-0449-a052-f55c-6fc8e8b36a83@kernel.org> (raw)
In-Reply-To: <20220507081710.117162-3-changfengnan@vivo.com>

On 2022/5/7 16:17, Fengnan Chang wrote:
> Since pvec have 15 pages, it not a multiple of 4, when write compressed
> pages, write in 64K as a unit, it will call pagevec_lookup_range_tag
> agagin, sometimes this will take a lot of time.
> Use onstack pages instead of pvec to mitigate this problem.
> 
> Signed-off-by: Fengnan Chang <changfengnan@vivo.com>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2022-07-11  9:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-07  8:17 [f2fs-dev] [PATCH v2 0/3] support compressed file write/read amplifiction Fengnan Chang via Linux-f2fs-devel
2022-05-07  8:17 ` [f2fs-dev] [PATCH v2 1/3] f2fs: intorduce f2fs_all_cluster_page_ready Fengnan Chang via Linux-f2fs-devel
2022-07-11  9:24   ` Chao Yu
2022-05-07  8:17 ` [f2fs-dev] [PATCH v2 2/3] f2fs: use onstack pages instead of pvec Fengnan Chang via Linux-f2fs-devel
2022-07-11  9:46   ` Chao Yu [this message]
2022-05-07  8:17 ` [f2fs-dev] [PATCH v2 3/3] f2fs: support compressed file write/read amplifiction Fengnan Chang via Linux-f2fs-devel
2022-07-10 12:40   ` fengnan chang
2022-07-11 10:10   ` Chao Yu
2022-06-03  2:13 ` [f2fs-dev] [PATCH v2 0/3] " fengnan chang

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=04cc6525-0449-a052-f55c-6fc8e8b36a83@kernel.org \
    --to=chao@kernel.org \
    --cc=changfengnan@vivo.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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.