From: "\"Zhou, Wenjian/周文剑\"" <zhouwj-fnst@cn.fujitsu.com>
To: Minfei Huang <mhuang@redhat.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: [PATCH v4] Improve the performance of --num-threads -d 31
Date: Thu, 24 Mar 2016 13:28:10 +0800 [thread overview]
Message-ID: <56F37AEA.3050306@cn.fujitsu.com> (raw)
In-Reply-To: <56EB96B8.7010103@cn.fujitsu.com>
Hello Minfei,
How do these two patches work?
--
Thanks
Zhou
On 03/18/2016 01:48 PM, "Zhou, Wenjian/周文剑" wrote:
> On 03/18/2016 12:16 PM, Minfei Huang wrote:
>> On 03/18/16 at 10:46am, "Zhou, Wenjian/周文剑" wrote:
>>> Hello Minfei,
>>>
>>> Since I can't produce the bug, I reviewed the patch and wrote an increment patch.
>>> Though there are some bugs in the increment patch,
>>> I wonder if the previous bug still exists with this patch.
>>> Could you help me confirm it?
>>
>> Ok. I will help verify this increasing patch.
>>
>
> Thank you very much.
>
>>>
>>> And I have another question.
>>> Did it only occur in patch v4?
>>
>> This issue doesn't exist in v3. I have pasted the test result with
>> --num-thread 32 in that thread.
>>
>> applied makedumpfile with option -d 31 --num-threads 32
>> real 3m3.533s
>
> Oh, then the patch in the previous mail may not work.
>
> I'm appreciated if you can also test the patch in this letter.
>
> I introduced semaphore to fix the bug in the v3.
> So I want to know if it is this which affects the result.
> The attached patch is based on v4, used to remove semaohore.
>
>
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2016-03-24 5:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 0:27 [PATCH v4] Improve the performance of --num-threads -d 31 Zhou Wenjian
2016-03-09 0:35 ` "Zhou, Wenjian/周文剑"
2016-03-11 1:00 ` "Zhou, Wenjian/周文剑"
2016-03-11 3:03 ` Minoru Usui
2016-03-11 3:10 ` "Zhou, Wenjian/周文剑"
2016-03-11 4:55 ` Atsushi Kumagai
2016-03-11 5:33 ` Minfei Huang
2016-03-15 6:34 ` Minfei Huang
2016-03-15 7:12 ` "Zhou, Wenjian/周文剑"
2016-03-15 7:38 ` Minfei Huang
2016-03-15 9:33 ` Minfei Huang
2016-03-16 1:55 ` "Zhou, Wenjian/周文剑"
2016-03-16 8:04 ` Minfei Huang
2016-03-16 8:24 ` Minfei Huang
2016-03-16 8:26 ` "Zhou, Wenjian/周文剑"
[not found] ` <B049E864-7426-4817-96FA-8E3CCA59CA24@redhat.com>
2016-03-16 8:59 ` "Zhou, Wenjian/周文剑"
2016-03-16 9:30 ` Minfei Huang
2016-03-15 8:35 ` "Zhou, Wenjian/周文剑"
2016-03-18 2:46 ` "Zhou, Wenjian/周文剑"
2016-03-18 4:16 ` Minfei Huang
2016-03-18 5:48 ` "Zhou, Wenjian/周文剑"
2016-03-24 5:28 ` "Zhou, Wenjian/周文剑" [this message]
2016-03-24 5:39 ` Minfei Huang
2016-03-25 2:57 ` Atsushi Kumagai
2016-03-28 1:23 ` "Zhou, Wenjian/周文剑"
2016-03-28 5:43 ` Atsushi Kumagai
2016-03-31 8:38 ` Minfei Huang
2016-03-31 9:09 ` "Zhou, Wenjian/周文剑"
2016-04-01 6:27 ` Minfei Huang
2016-04-01 11:21 ` "Zhou, Wenjian/周文剑"
2016-04-01 13:15 ` Minfei Huang
2016-04-04 5:46 ` Atsushi Kumagai
2016-04-05 9:18 ` Minfei Huang
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=56F37AEA.3050306@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