[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20130701125345.c4a383c7b8345f9c5ae54023@linux-foundation.org>
Date: Mon, 1 Jul 2013 12:53:45 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Maxim Uvarov <muvarov@...il.com>
Cc: HATAYAMA Daisuke <d.hatayama@...fujitsu.com>,
Atsushi Kumagai <kumagai-atsushi@....nes.nec.co.jp>,
riel@...hat.com, kexec@...ts.infradead.org, hughd@...gle.com,
linux-kernel@...r.kernel.org, lisa.mitchell@...com,
vgoyal@...hat.com, linux-mm@...ck.org, zhangyanfei@...fujitsu.com,
ebiederm@...ssion.com, kosaki.motohiro@...fujitsu.com,
walken@...gle.com, cpw@....com, jingbai.ma@...com
Subject: Re: [PATCH v8 9/9] vmcore: support mmap() on /proc/vmcore
On Mon, 1 Jul 2013 18:34:43 +0400 Maxim Uvarov <muvarov@...il.com> wrote:
> 2013/7/1 HATAYAMA Daisuke <d.hatayama@...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 have no point of comparison here. Is this performance good, or is
the mmap-based approach still a lot more expensive?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists