From: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
To: Cliff Wickman <cpw@sgi.com>
Cc: kexec@lists.infradead.org, kumagai-atsushi@mxc.nes.nec.co.jp
Subject: Re: A few patches to consider
Date: Fri, 30 Aug 2013 10:33:09 +0900 [thread overview]
Message-ID: <521FF655.8000909@jp.fujitsu.com> (raw)
In-Reply-To: <E1VEnuJ-0000Jl-CC@eag09.americas.sgi.com>
(2013/08/29 7:08), Cliff Wickman wrote:
> From: Cliff Wickman <cpw@sgi.com>
>
> I am submitting 6 patches that I have found helpful in speeding the dump
> process or clarifying the progress report.
> They are not a series, and should not be interdependent. But if you
> find any dependencies I apply them in this order:
> [PATCH] makedumpfile: reverse -c and -p if using snappy compression
> [PATCH] makedumpfile: use non-cyclic when possible
> [PATCH] makedumpfile: shorten cyclic exclude-unnecessary passes
> [PATCH] makedumpfile: shorten cyclic unnecessary-page scans
> [PATCH] makedumpfile: show needed memory
> [PATCH] makedumpfile: search for a debug vmlinux
>
> The last one (search for a debug vmlinux) is useful in identifying huge
> pages with the PG_head/PG-tail flags. There was a patch from Petr Tesarik
> that enables that huge page filtering. I don't think you are taking that one
> as-is, but are reworking it. Seems like Hatayama-san was doing that work.
No. If I have good memory, Kumagai-san was investigating how to integrate
huge page filtering into current memory types currently supported by
makedumpfile.
--
Thanks.
HATAYAMA, Daisuke
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-08-30 1:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 22:08 A few patches to consider Cliff Wickman
2013-08-30 1:33 ` HATAYAMA Daisuke [this message]
2013-09-18 3:00 ` Atsushi Kumagai
2013-09-19 2:12 ` HATAYAMA Daisuke
2013-09-19 5:00 ` Atsushi Kumagai
2013-09-20 20:52 ` Petr Tesarik
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=521FF655.8000909@jp.fujitsu.com \
--to=d.hatayama@jp.fujitsu.com \
--cc=cpw@sgi.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
/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