Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Cliff Wickman <cpw@sgi.com>
To: kexec@lists.infradead.org
Subject: [PATCH 0/2] time and space saving patches for large memories
Date: Tue, 9 Dec 2014 16:04:27 -0600	[thread overview]
Message-ID: <20141209220427.GA18652@sgi.com> (raw)

From: Cliff Wickman <cpw@sgi.com>

Back in early 2014 I submitted several patches for your consideration, most of
which concerned saving time and disk space when dumping very large memories.

I offer two of them again, as being the most important elements for the
practical dumping of very large memories.

[PATCH 1/2] use raw i/o and root device to use less memory
[PATCH 2/2] exclude page structures of non-dumped pages
  The second patch has a few dependencies on the first. But they are logically
  separate.  
  They apply to the 1.5.7 source.

As an example of the importance of these two concepts:
 We dump a 2TB system using crashkernel=450M.
 Without the patches we write a 3.6G dump in about 12 minutes.
 With the patches we write a 590M dump in about 4 minutes.
And the savings multiply as memory size grows.

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

                 reply	other threads:[~2014-12-09 22:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20141209220427.GA18652@sgi.com \
    --to=cpw@sgi.com \
    --cc=kexec@lists.infradead.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