Linux-EROFS Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Chunhai Guo <guochunhai@vivo.com>, xiang@kernel.org
Cc: linux-erofs@lists.ozlabs.org, huyue2@coolpad.com
Subject: Re: [PATCH v2] erofs: add a global page pool for lz4 decompression
Date: Tue, 9 Jan 2024 21:08:18 +0800	[thread overview]
Message-ID: <d8a104d4-1a58-423a-ba12-ea82d622de48@linux.alibaba.com> (raw)
In-Reply-To: <20240109074143.4138783-1-guochunhai@vivo.com>

Hi Chunhai,

On 2024/1/9 15:41, Chunhai Guo wrote:
> Using a global page pool for LZ4 decompression significantly reduces the
> time spent on page allocation in low memory scenarios.
> 
> The table below shows the reduction in time spent on page allocation for
> LZ4 decompression when using a global page pool.  The results were
> obtained from multi-app launch benchmarks on ARM64 Android devices
> running the 5.15 kernel with an 8-core CPU and 8GB of memory.  In the
> benchmark, we launched 16 frequently-used apps, and the camera app was
> the last one in each round. The data in the table is the average time of
> camera app for each round.
> After using the page pool, there was an average improvement of 150ms in
> the launch time of the camera app, which was obtained from systrace log.
> +--------------+---------------+--------------+---------+
> |              | w/o page pool | w/ page pool |  diff   |
> +--------------+---------------+--------------+---------+
> | Average (ms) |     3434      |      21      | -99.38% |
> +--------------+---------------+--------------+---------+
> 
> Based on the benchmark logs, 64 pages are sufficient for 95% of
> scenarios. This value can be adjusted from the module parameter. The
> default value is 0.
> 
> This patch currently only supports the LZ4 decompressor, other
> decompressors will be supported in the next step.
> 
> Signed-off-by: Chunhai Guo <guochunhai@vivo.com>


This patch looks good to me, yet we're in the merge window for v6.8.
I will address it after -rc1 is out since no stable tag these days.

Also it would be better to add some results of changing max_distance
if you have more time to test.

Thanks,
Gao Xiang

  reply	other threads:[~2024-01-09 13:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-09  7:41 [PATCH v2] erofs: add a global page pool for lz4 decompression Chunhai Guo via Linux-erofs
2024-01-09 13:08 ` Gao Xiang [this message]
2024-01-10  6:45   ` Chunhai Guo via Linux-erofs
2024-01-12  1:58     ` Chunhai Guo via Linux-erofs
2024-01-22  4:41       ` Gao Xiang

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=d8a104d4-1a58-423a-ba12-ea82d622de48@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=guochunhai@vivo.com \
    --cc=huyue2@coolpad.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=xiang@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