From: Coiby Xu <coxu@redhat.com>
To: cryptsetup@lists.linux.dev
Subject: How to estimate the upper bound of the peak memory consumption of cryptsetup itself?
Date: Thu, 16 Jun 2022 12:43:39 +0800 [thread overview]
Message-ID: <20220616044339.376qlipk5h2omhx2@Rk> (raw)
Hi,
Recently, I notice cryptsetup itself consumes significant amount of
memory (~256M) when estimating the memory requirement for dumping vmcore
to a LUKS-encrypted disk,
$ time -v cryptsetup luksOpen encrypted.img volume --key-file mykey.keyfile | grep "Maximum resident set size"
Maximum resident set size (kbytes): 1309828
$ cryptsetup luksDump encrypted.img
...
Keyslots:
0: luks2
PBKDF: argon2id
Memory: 1048576
...
So is there a way to estimate the upper bound of the peak memory
consumption of cryptsetup itself without running cryptsetup?
Thanks!
--
Best regards,
Coiby
next reply other threads:[~2022-06-16 4:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 4:43 Coiby Xu [this message]
2022-06-18 15:12 ` How to estimate the upper bound of the peak memory consumption of cryptsetup itself? Milan Broz
2022-06-20 0:19 ` Coiby Xu
2022-06-24 9:14 ` Milan Broz
2022-06-24 10:49 ` Coiby Xu
2022-06-24 12:22 ` Milan Broz
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=20220616044339.376qlipk5h2omhx2@Rk \
--to=coxu@redhat.com \
--cc=cryptsetup@lists.linux.dev \
/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.