All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Coiby Xu <coxu@redhat.com>, cryptsetup@lists.linux.dev
Subject: Re: How to estimate the upper bound of the peak memory consumption of cryptsetup itself?
Date: Sat, 18 Jun 2022 17:12:56 +0200	[thread overview]
Message-ID: <11d06783-c697-db7d-ed09-237d389aa07d@gmail.com> (raw)
In-Reply-To: <20220616044339.376qlipk5h2omhx2@Rk>

On 16/06/2022 06:43, Coiby Xu wrote:
> 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?

As you already found, the major memory consumption is by memory-hard KDF.
But this memory is used only while calculating keyslot encryption key,
it is released immediately after the Argon call is finished.
I do not think we have better estimation here.

(Another story is locking all memory, including big areas used by libc,
but that should not be problem here, I hope.)

Milan

  reply	other threads:[~2022-06-18 15:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16  4:43 How to estimate the upper bound of the peak memory consumption of cryptsetup itself? Coiby Xu
2022-06-18 15:12 ` Milan Broz [this message]
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=11d06783-c697-db7d-ed09-237d389aa07d@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=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.