linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Maxim Uvarov <muvarov@gmail.com>
To: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
Cc: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>,
	riel@redhat.com, kexec@lists.infradead.org, hughd@google.com,
	linux-kernel@vger.kernel.org, lisa.mitchell@hp.com,
	vgoyal@redhat.com, linux-mm@kvack.org,
	zhangyanfei@cn.fujitsu.com, ebiederm@xmission.com,
	kosaki.motohiro@jp.fujitsu.com, akpm@linux-foundation.org,
	walken@google.com, cpw@sgi.com, jingbai.ma@hp.com
Subject: Re: [PATCH v8 9/9] vmcore: support mmap() on /proc/vmcore
Date: Mon, 1 Jul 2013 18:34:43 +0400	[thread overview]
Message-ID: <CAJGZr0Jwy6OLADBO9GExWVbwG_LMk41ZsSMZKvWmwcA9StVZQA@mail.gmail.com> (raw)
In-Reply-To: <51D0C500.4060108@jp.fujitsu.com>

[-- Attachment #1: Type: text/plain, Size: 2582 bytes --]

2013/7/1 HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>

> (2013/06/29 1:40), Maxim Uvarov wrote:
>
>> Did test on 1TB machine. Total vmcore capture and save took 143 minutes
>> while vmcore size increased from 9Gb to 59Gb.
>>
>> Will do some debug for that.
>>
>> Maxim.
>>
>
> Please show me your kdump configuration file and tell me what you did in
> the test and how you confirmed the result.
>
>
Hello Hatayama,

I re-run tests in dev env. I took your latest kernel patchset from
patchwork for vmcore + devel branch of makedumpfile + fix to open and write
to /dev/null. Run this test on 1Tb memory machine with memory used by some
user space processes. crashkernel=384M.

Please see my results for makedumpfile process work:
[gzip compression]
-c -d31 /dev/null
real 37.8 m
user 29.51 m
sys 7.12 m

[no compression]
-d31 /dev/null
real 27 m
user 23 m
sys   4 m

[no compression, disable cyclic mode]
-d31 --non-cyclic /dev/null
real 26.25 m
user 23 m
sys 3.13 m

[gzip compression]
-c -d31 /dev/null
% time     seconds  usecs/call     calls    errors syscall
------ ----------- ----------- --------- --------- ----------------
 54.75   38.840351         110    352717           mmap
 44.55   31.607620          90    352716         1 munmap
  0.70    0.497668           0  25497667           brk
  0.00    0.000356           0    111920           write
  0.00    0.000280           0    111904           lseek
  0.00    0.000025           4         7           open
  0.00    0.000000           0       473           read
  0.00    0.000000           0         7           close
  0.00    0.000000           0         3           fstat
  0.00    0.000000           0         1           getpid
  0.00    0.000000           0         1           execve
  0.00    0.000000           0         1           uname
  0.00    0.000000           0         2           unlink
  0.00    0.000000           0         1           arch_prctl
------ ----------- ----------- --------- --------- ----------------
100.00   70.946300              26427420         1 total


I used 2.6.39 kernel + your patches due to mine machine successfully work
with it. I think that kernel version is not sufficient here due to
/proc/vmcore is  very isolated.

Is that the same numbers which you have?

Interesting is that makedumpfile almost all time works in user space. And
in case without compression  and without disk I/O process time is not
significantly reduced. What is the bottleneck in 'copy dump' phase?

Thank you,
Maxim.




> --
> Thanks.
> HATAYAMA, Daisuke
>
>


-- 
Best regards,
Maxim Uvarov

[-- Attachment #2: Type: text/html, Size: 3462 bytes --]

  reply	other threads:[~2013-07-01 14:34 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23  5:24 [PATCH v8 0/9] kdump, " HATAYAMA Daisuke
2013-05-23  5:25 ` [PATCH v8 1/9] vmcore: clean up read_vmcore() HATAYAMA Daisuke
2013-05-23  5:25 ` [PATCH v8 2/9] vmcore: allocate buffer for ELF headers on page-size alignment HATAYAMA Daisuke
2013-05-23 14:22   ` Vivek Goyal
2013-05-23 21:46   ` Andrew Morton
2013-05-23  5:25 ` [PATCH v8 3/9] vmcore: treat memory chunks referenced by PT_LOAD program header entries in page-size boundary in vmcore_list HATAYAMA Daisuke
2013-05-23 21:49   ` Andrew Morton
2013-05-24 13:12     ` Vivek Goyal
2013-05-27  0:13       ` HATAYAMA Daisuke
2013-05-23  5:25 ` [PATCH v8 4/9] vmalloc: make find_vm_area check in range HATAYAMA Daisuke
2013-05-23  5:25 ` [PATCH v8 5/9] vmalloc: introduce remap_vmalloc_range_partial HATAYAMA Daisuke
2013-05-23 22:00   ` Andrew Morton
2013-05-23  5:25 ` [PATCH v8 6/9] vmcore: allocate ELF note segment in the 2nd kernel vmalloc memory HATAYAMA Daisuke
2013-05-23 14:28   ` Vivek Goyal
2013-05-23 22:17   ` Andrew Morton
2013-05-23  5:25 ` [PATCH v8 7/9] vmcore: Allow user process to remap ELF note segment buffer HATAYAMA Daisuke
2013-05-23 14:32   ` Vivek Goyal
2013-05-23  5:25 ` [PATCH v8 8/9] vmcore: calculate vmcore file size from buffer size and total size of vmcore objects HATAYAMA Daisuke
2013-05-23 14:34   ` Vivek Goyal
2013-05-23  5:25 ` [PATCH v8 9/9] vmcore: support mmap() on /proc/vmcore HATAYAMA Daisuke
2013-05-23 22:24   ` Andrew Morton
2013-05-24  9:02     ` Maxim Uvarov
2013-05-27  1:49       ` HATAYAMA Daisuke
2013-05-30  9:14         ` Maxim Uvarov
2013-05-30  9:26           ` Zhang Yanfei
2013-05-30 10:30             ` Maxim Uvarov
2013-06-03  8:43               ` Atsushi Kumagai
2013-06-04 15:34                 ` Maxim Uvarov
2013-06-07  1:11                   ` Zhang Yanfei
2013-06-28 16:40                 ` Maxim Uvarov
2013-06-30 23:53                   ` HATAYAMA Daisuke
2013-07-01 14:34                     ` Maxim Uvarov [this message]
2013-07-01 19:53                       ` Andrew Morton
2013-07-02  7:00                         ` Maxim Uvarov
2013-06-06 21:31   ` Arnd Bergmann
2013-06-07  1:01     ` HATAYAMA Daisuke
2013-06-07 18:34       ` Arnd Bergmann
2013-06-08 10:42         ` HATAYAMA Daisuke
2013-05-23 14:35 ` [PATCH v8 0/9] kdump, " Vivek Goyal

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=CAJGZr0Jwy6OLADBO9GExWVbwG_LMk41ZsSMZKvWmwcA9StVZQA@mail.gmail.com \
    --to=muvarov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cpw@sgi.com \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=ebiederm@xmission.com \
    --cc=hughd@google.com \
    --cc=jingbai.ma@hp.com \
    --cc=kexec@lists.infradead.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=kumagai-atsushi@mxc.nes.nec.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lisa.mitchell@hp.com \
    --cc=riel@redhat.com \
    --cc=vgoyal@redhat.com \
    --cc=walken@google.com \
    --cc=zhangyanfei@cn.fujitsu.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