All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jingbai Ma <jingbai.ma@hp.com>
To: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Wang, Jin (Steven)" <jin.wang@hp.com>,
	Jingbai Ma <jingbai.ma@hp.com>,
	"Mitchell, Lisa (MCLinux in Fort Collins)" <lisa.mitchell@hp.com>,
	HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
	"kumagai-atsushi@mxc.nes.nec.co.jp"
	<kumagai-atsushi@mxc.nes.nec.co.jp>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	"Croxon, Nigel" <nigel.croxon@hp.com>,
	cpw@sgi.com, Vivek Goyal <vgoyal@redhat.com>
Subject: makedumpfile 1.5.4 + kernel 3.11-rc2+ 4TB tests
Date: Fri, 26 Jul 2013 19:42:39 +0800	[thread overview]
Message-ID: <51F260AF.7010409@hp.com> (raw)

Hi,

I have run some tests with makedumpfile 1.5.4 and upstream kernel 
3.11-rc2+ on a machine with 4TB memory, here is testing results:

Test environment:
Machine: HP ProLiant DL980 G7 with 4TB RAM.
CPU: Intel(R) Xeon(R) CPU E7- 2860  @ 2.27GHz (8 sockets, 10 cores)
(Only 1 CPU was enabled the 2nd kernel)
Kernel: 3.11.0-rc2+ (at patch b3a3a9c441e2c8f6b6760de9331023a7906a4ac6)
crashkernel=384MB
vmcore size: 4.0TB
Dump file size: 15GB
All measured time from debug message of makedumpfile.
As a comparison, I also have tested makedumpfile 1.5.3.

(all time in seconds)
                      Excluding pages   Copy data   Total
makedumpfile 1.5.3          468         1182       1650
makedumpfile 1.5.4           93          518        611


So it seems there is a great performance improvement by the mmap mechanism.

--
Thanks,
Jingbai Ma

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

WARNING: multiple messages have this Message-ID (diff)
From: Jingbai Ma <jingbai.ma@hp.com>
To: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "kumagai-atsushi@mxc.nes.nec.co.jp" 
	<kumagai-atsushi@mxc.nes.nec.co.jp>,
	HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
	Vivek Goyal <vgoyal@redhat.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	cpw@sgi.com, "Mitchell,
	Lisa (MCLinux in Fort Collins)" <lisa.mitchell@hp.com>,
	"Croxon, Nigel" <nigel.croxon@hp.com>,
	Jingbai Ma <jingbai.ma@hp.com>,
	"Wang, Jin (Steven)" <jin.wang@hp.com>
Subject: makedumpfile 1.5.4 + kernel 3.11-rc2+ 4TB tests
Date: Fri, 26 Jul 2013 19:42:39 +0800	[thread overview]
Message-ID: <51F260AF.7010409@hp.com> (raw)

Hi,

I have run some tests with makedumpfile 1.5.4 and upstream kernel 
3.11-rc2+ on a machine with 4TB memory, here is testing results:

Test environment:
Machine: HP ProLiant DL980 G7 with 4TB RAM.
CPU: Intel(R) Xeon(R) CPU E7- 2860  @ 2.27GHz (8 sockets, 10 cores)
(Only 1 CPU was enabled the 2nd kernel)
Kernel: 3.11.0-rc2+ (at patch b3a3a9c441e2c8f6b6760de9331023a7906a4ac6)
crashkernel=384MB
vmcore size: 4.0TB
Dump file size: 15GB
All measured time from debug message of makedumpfile.
As a comparison, I also have tested makedumpfile 1.5.3.

(all time in seconds)
                      Excluding pages   Copy data   Total
makedumpfile 1.5.3          468         1182       1650
makedumpfile 1.5.4           93          518        611


So it seems there is a great performance improvement by the mmap mechanism.

--
Thanks,
Jingbai Ma

             reply	other threads:[~2013-07-26 11:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 11:42 Jingbai Ma [this message]
2013-07-26 11:42 ` makedumpfile 1.5.4 + kernel 3.11-rc2+ 4TB tests Jingbai Ma
2013-07-26 13:23 ` Vivek Goyal
2013-07-26 13:23   ` 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=51F260AF.7010409@hp.com \
    --to=jingbai.ma@hp.com \
    --cc=cpw@sgi.com \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=ebiederm@xmission.com \
    --cc=jin.wang@hp.com \
    --cc=kexec@lists.infradead.org \
    --cc=kumagai-atsushi@mxc.nes.nec.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lisa.mitchell@hp.com \
    --cc=nigel.croxon@hp.com \
    --cc=vgoyal@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.