From: Harald Freudenberger <freude@linux.ibm.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: agk@redhat.com, snitzer@kernel.org, ifranzki@linux.ibm.com,
linux-s390@vger.kernel.org, dm-devel@lists.linux.dev,
herbert@gondor.apana.org.au, dengler@linux.ibm.com
Subject: Re: [PATCH v1 1/1] dm-integrity: Implement asynch digest support
Date: Fri, 17 Jan 2025 14:31:25 +0100 [thread overview]
Message-ID: <3d8e8b33e4ade05a2bd0e99583444f0f@linux.ibm.com> (raw)
In-Reply-To: <b541f1bb-5287-7600-77ce-ceed5903e554@redhat.com>
On 2025-01-15 18:29, Mikulas Patocka wrote:
> Hi
>
> The ahash interface is slower than the shash interface for synchronous
> implementations, so the patch is basically slowing down the common
> case.
> See the upstream commit b76ad8844234bd0d394105d7d784cd05f1bf269a for an
> explanation in dm-verity.
>
> Do you have some benchmark that shows how much does it help on s390x?
> So,
> that we can evaluate whether the added complexity is worth the
> performance
> improvement or not.
>
> Mikulas
>
Just a short sniff test on my development system (s390x with 32GB RAM,
16 CPUs).
When I run a dm-integrity format command on a 16G loopback file backed
up by tempfs
I get this on a fedora40 with fresh build v6.13-rc7 kernel:
integritysetup format /dev/loop0 --integrity sha256 --sector-size 4096
...
Finished, time 00m08s, 15 GiB written, speed 1.8 GiB/s
and with the same kernel + my dm-integrity async patch:
Finished, time 00m09s, 15 GiB written, speed 1.7 GiB/s
However, I'll run some more sophisticated performance measurements
during
the weekend.
Harald Freudenberger
next prev parent reply other threads:[~2025-01-17 13:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 16:46 [PATCH v1 0/1] dm-integrity: Implement asynch digest support Harald Freudenberger
2025-01-15 16:46 ` [PATCH v1 1/1] " Harald Freudenberger
2025-01-15 17:29 ` Mikulas Patocka
2025-01-17 13:31 ` Harald Freudenberger [this message]
2025-01-22 17:00 ` Harald Freudenberger
2025-01-27 17:57 ` Mikulas Patocka
2025-01-15 17:37 ` Eric Biggers
2025-01-16 7:33 ` Harald Freudenberger
2025-01-16 8:03 ` Eric Biggers
2025-01-16 9:00 ` Harald Freudenberger
2025-01-16 9:12 ` Herbert Xu
2025-01-16 17:54 ` Eric Biggers
2025-01-17 6:21 ` Herbert Xu
2025-01-17 7:57 ` Eric Biggers
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=3d8e8b33e4ade05a2bd0e99583444f0f@linux.ibm.com \
--to=freude@linux.ibm.com \
--cc=agk@redhat.com \
--cc=dengler@linux.ibm.com \
--cc=dm-devel@lists.linux.dev \
--cc=herbert@gondor.apana.org.au \
--cc=ifranzki@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@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