From: Mike Snitzer <snitzer@kernel.org>
To: Nathan Huckleberry <nhuck@google.com>, mpatocka@redhat.com
Cc: linux-kernel@vger.kernel.org, Eric Biggers <ebiggers@kernel.org>,
dm-devel@redhat.com, Sami Tolvanen <samitolvanen@google.com>,
Alasdair Kergon <agk@redhat.com>
Subject: Re: dm-verity: Remove WQ_UNBOUND.
Date: Thu, 2 Feb 2023 11:41:25 -0500 [thread overview]
Message-ID: <Y9vnte1xP5T+nZ6j@redhat.com> (raw)
In-Reply-To: <20230202012348.885402-1-nhuck@google.com>
On Wed, Feb 01 2023 at 8:23P -0500,
Nathan Huckleberry <nhuck@google.com> wrote:
> Setting WQ_UNBOUND increases scheduler latency on ARM64. This is likely
> due to the asymmetric architecture of ARM64 processors.
>
> I've been unable to reproduce the results that claim WQ_UNBOUND gives a
> performance boost on x86-64.
>
> This flag is causing performance issues for multiple subsystems within
> Android. Notably, the same slowdown exists for decompression with
> EROFS.
>
> | open-prebuilt-camera | WQ_UNBOUND | ~WQ_UNBOUND |
> |-----------------------|------------|---------------|
> | verity wait time (us) | 11746 | 119 (-98%) |
> | erofs wait time (us) | 357805 | 174205 (-51%) |
>
> | sha256 ramdisk random read | WQ_UNBOUND | ~WQ_UNBOUND |
> |----------------------------|-----------=---|-------------|
> | arm64 (accelerated) | bw=42.4MiB/s | bw=212MiB/s |
> | arm64 (generic) | bw=16.5MiB/s | bw=48MiB/s |
> | x86_64 (generic) | bw=233MiB/s | bw=230MiB/s |
>
> Cc: Sami Tolvanen <samitolvanen@google.com>
> Cc: Eric Biggers <ebiggers@kernel.org>
> Signed-off-by: Nathan Huckleberry <nhuck@google.com>
> ---
> drivers/md/dm-verity-target.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/md/dm-verity-target.c b/drivers/md/dm-verity-target.c
> index ccf5b852fbf7..020fd2341025 100644
> --- a/drivers/md/dm-verity-target.c
> +++ b/drivers/md/dm-verity-target.c
> @@ -1399,8 +1399,8 @@ static int verity_ctr(struct dm_target *ti, unsigned argc, char **argv)
> goto bad;
> }
>
> - /* WQ_UNBOUND greatly improves performance when running on ramdisk */
> - wq_flags = WQ_MEM_RECLAIM | WQ_UNBOUND;
> + wq_flags = WQ_MEM_RECLAIM;
> +
> /*
> * Using WQ_HIGHPRI improves throughput and completion latency by
> * reducing wait times when reading from a dm-verity device.
> --
> 2.39.1.456.gfc5497dd1b-goog
Hi,
I've discussed with Mikulas, tweaked your patch slightly but accepted
your change, please see:
https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-6.3&id=6f30cc248507ee96c22ff4c3cbc86099ff12b7a9
Thanks,
Mike
next prev parent reply other threads:[~2023-02-02 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 1:23 [PATCH] " Nathan Huckleberry
2023-02-02 16:04 ` [dm-devel] " Mikulas Patocka
2023-02-07 22:54 ` Nathan Huckleberry
2023-02-02 16:41 ` Mike Snitzer [this message]
2023-02-02 19:11 ` Nathan Huckleberry
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=Y9vnte1xP5T+nZ6j@redhat.com \
--to=snitzer@kernel.org \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=ebiggers@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=nhuck@google.com \
--cc=samitolvanen@google.com \
/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
Powered by JetHome