From: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
To: d.hatayama@jp.fujitsu.com
Cc: ptesarik@suse.cz, kexec@lists.infradead.org, cpw@sgi.com
Subject: Re: A few patches to consider
Date: Wed, 18 Sep 2013 12:00:48 +0900 [thread overview]
Message-ID: <52391760.9000106@mxc.nes.nec.co.jp> (raw)
In-Reply-To: <521FF655.8000909@jp.fujitsu.com>
(2013/08/30 10:33), HATAYAMA Daisuke wrote:
> (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.
Yes, I was investigating it but I'm not working for it now.
I think main features should work without vmlinux,
but it was impossible about his patch as said by himself:
> This patch depends on exporting the relevant PG_* flags from the
> kernel (in VMCOREINFO), and that's where I got stuck, because depending
> on the number of available bits for the page flags, the kernel either
> has PG_head and PG_tail, or only PG_compound, so I needed a #ifdef, and
> the kernel maintainers didn't like the conditional.
> I can restart the discussion with kernel maintainers and see what I can do
Therefore, I waited that his work is finished and I was going to continue
my work, but I didn't say my thinking definitely, sorry.
Anyway, I should cooperate with Petr to develop huge page filtering,
so could you let me know the status of your work ?
Thanks
Atsushi Kumagai
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-09-18 3:07 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
2013-09-18 3:00 ` Atsushi Kumagai [this message]
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=52391760.9000106@mxc.nes.nec.co.jp \
--to=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=cpw@sgi.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=kexec@lists.infradead.org \
--cc=ptesarik@suse.cz \
/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