Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "\"Zhou, Wenjian/周文剑\"" <zhouwj-fnst@cn.fujitsu.com>
To: Minfei Huang <mhuang@redhat.com>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH v2] Improve the performance of --num-threads -d 31
Date: Tue, 23 Feb 2016 13:47:18 +0800	[thread overview]
Message-ID: <56CBF266.8070107@cn.fujitsu.com> (raw)
In-Reply-To: <20160223052616.GA19420@dhcp-128-25.nay.redhat.com>

Hello, Minfei,

Does it occur every time?
If not, I think I have known the reason.

-- 
Thanks
Zhou

On 02/23/2016 01:26 PM, Minfei Huang wrote:
> On 02/23/16 at 12:58am, Minfei Huang wrote:
>> On 02/17/16 at 03:05pm, Zhou Wenjian wrote:
>>> The new implementation won't do the extra work for filtered pages any
>>> more. So the performance of -d 31 is close to that of serial processing.
>>
>> Hi, Wenjian.
>>
>> kdump:/# time bash -x a.sh makedumpfile vmcore02 1 --num-threads 128
>> + makedumpfile --num-threads -l --message-level 1 -d 31 /proc/vmcore /kdumproot/home//var/crash/127.0.0.1-2016-02-22-23:22:36/vmcore02
>
> Please ignore this benchmark, since there is no parameter passed to
> option num-threads. Following is my new test result which is generated
> in 1st kernel.
>
> 127.0.0.1-2016-02-22-19\:08\:17/vmcore01 is generated by makedumpfile
> with -d 31 in 2nd kernel.
>>
>> Command makedumpfile is complied with this patch on version 1.5.9, and
>> makedumpfile.backup is complied on version 1.5.7.
>>
>> The compressed file vmcore is 67G filtered out from 4T memory.
>
> [crash]# time makedumpfile -l --message-level 1 -d 31 127.0.0.1-2016-02-22-19\:08\:17/vmcore01 vmcore10
> Copying data                       : [100.0 %] /
>
> real    7m25.492s
> user    6m37.386s
> sys 0m47.801s
> [crash]# time makedumpfile.backup -l --message-level 1 -d 31 127.0.0.1-2016-02-22-19\:08\:17/vmcore01 vmcore11
> Copying data                       : [100.0 %] -
>
> real    7m15.784s
> user    6m28.829s
> sys 0m46.656s
>
> [crash]# time makedumpfile --num-threads 128 -l --message-level 1 -d 31 127.0.0.1-2016-02-22-19\:08\:17/vmcore01
> vmcore14
> Copying data                       : [ 99.7 %] |
>
> Never return from makedumpfile.
>
> There are more than 128 cpus plugged in this machine.
>
> Thanks
> Minfei
>
>






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

  reply	other threads:[~2016-02-23  5:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17  7:05 [PATCH v2] Improve the performance of --num-threads -d 31 Zhou Wenjian
2016-02-22 16:58 ` Minfei Huang
2016-02-23  5:26   ` Minfei Huang
2016-02-23  5:47     ` "Zhou, Wenjian/周文剑" [this message]
2016-02-24  1:43       ` Minfei Huang
2016-02-24  2:20         ` "Zhou, Wenjian/周文剑"
2016-02-24  2:24           ` Minfei Huang
2016-03-01  6:59             ` "Zhou, Wenjian/周文剑"
2016-03-01  8:16               ` Minfei Huang
2016-03-02 10:25                 ` Minfei Huang
2016-03-04  0:59                   ` Minoru Usui
2016-03-04  4:17                     ` Minfei Huang
2016-03-01  7:20             ` "Zhou, Wenjian/周文剑"
2016-03-01  8:17               ` Minfei Huang
2016-02-23  1:32 ` Minoru Usui
2016-02-23  3:45   ` "Zhou, Wenjian/周文?"
2016-02-23  8:00     ` Minoru Usui
2016-02-23  8:29       ` "Zhou, Wenjian/周文?"
2016-02-24  0:45         ` Minoru Usui
2016-03-01  7:49           ` "Zhou, Wenjian/周文?"
2016-03-02  3:05             ` Minoru Usui
2016-03-02  3:16               ` Minoru Usui
2016-03-02  3:59               ` "Zhou, Wenjian/周文?"
2016-03-02  6:23                 ` Minoru Usui
2016-02-24  8:13 ` Minoru Usui
2016-03-01  7:34   ` "Zhou, Wenjian/周文?"

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=56CBF266.8070107@cn.fujitsu.com \
    --to=zhouwj-fnst@cn.fujitsu.com \
    --cc=kexec@lists.infradead.org \
    --cc=mhuang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox