From: "Daniel Walker (danielwa)" <danielwa@cisco.com>
To: Guilherme Piccoli <gpiccoli@canonical.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"xe-linux-external(mailer list)" <xe-linux-external@cisco.com>
Subject: Re: [REQUEST] makedumpfile: stream compress flat ELF format with libz
Date: Tue, 12 May 2020 18:56:33 +0000 [thread overview]
Message-ID: <20200512185632.GQ31850@zorba> (raw)
In-Reply-To: <CAHD1Q_zghTM0ahkc-MLaRktC356YrQX_yg6bGn9pFXuxY3enrA@mail.gmail.com>
On Tue, May 12, 2020 at 03:32:25PM -0300, Guilherme Piccoli wrote:
> Sure, I understood that. I'm curious though about the memory
> consumption of the compression operation, or put in other words: do we
> need to increase crashkernel reserved memory if we plan to use your
> gzip approach?
> It's good to be sure about this, to evaluate the trade-off of core
> file size vs. necessary reserved memory.
I'm not sure. I didn't measure this, but from my experience makedumpfile uses
more memory during dumping than gzip uses for compression. If our dump kernels
run out of memory it's usually something inside makedumpfile when it's removing
pages or something along those lines.
Daniel
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2020-05-12 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 17:25 [REQUEST] makedumpfile: stream compress flat ELF format with libz Daniel Walker (danielwa)
2020-05-12 17:38 ` John Donnelly
2020-05-12 17:45 ` Daniel Walker (danielwa)
2020-05-12 18:14 ` Guilherme Piccoli
2020-05-12 18:27 ` Daniel Walker (danielwa)
2020-05-12 18:32 ` Guilherme Piccoli
2020-05-12 18:56 ` Daniel Walker (danielwa) [this message]
2020-05-12 19:20 ` HAGIO KAZUHITO(萩尾 一仁)
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=20200512185632.GQ31850@zorba \
--to=danielwa@cisco.com \
--cc=gpiccoli@canonical.com \
--cc=kexec@lists.infradead.org \
--cc=xe-linux-external@cisco.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