How to estimate the upper bound of the peak memory consumption of cryptsetup itself?

[Coiby Xu <coxu@redhat.com>]

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