From: Ye Xiaolong <xiaolong.ye@intel.com>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [x86/mm] c4c3c3c2d0: will-it-scale.per_process_ops -61.0% regression
Date: Thu, 19 Oct 2017 13:57:25 +0800 [thread overview]
Message-ID: <20171019055725.GA22668@yexl-desktop> (raw)
In-Reply-To: <20171018081109.mj6lzzihxmlle3b6@pd.tnic>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
Hi, ying
On 10/18, Borislav Petkov wrote:
>On Wed, Oct 18, 2017 at 09:59:02AM +0800, Ye Xiaolong wrote:
>> 2017-10-14 23:43:02 ./runtest.py context_switch1 295 process 44
>> tasks,processes,processes_idle,threads,threads_idle,linear
>> 0,0,100,0,100,0
>> 44,7723745,22.45,0,0.00,0
>>
>> per_process_ops = 7723745 / 44 = 175540
>
>What is that 7723745 value? 44 too?
>
>Please explain it in plain english and not in the context of some script
>you're running. Just assume I don't know *anything* about will-it-scale.
>How would you explain what those numbers are, to me?
Could you suggest better wording to describe the meaning of metric "will-it-scale.per_process_ops"?
Thanks,
Xiaolong
>
>And then consider adding boilerplate text to your reports *explaining*
>what you're measuring because as it is now, people are left wondering
>WTF is going on.
>
>> percent -61% is computed by (174892 - 448554) / 448554
>
>Ok, that I understand.
>
>Thx.
>
>--
>Regards/Gruss,
> Boris.
>
>Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2017-10-19 5:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 16:50 [RFC PATCH] x86/mm: Flush more aggressively in lazy TLB mode Andy Lutomirski
2017-10-09 17:02 ` Borislav Petkov
2017-10-09 17:36 ` Borislav Petkov
2017-10-09 17:50 ` Andy Lutomirski
2017-10-09 18:08 ` Borislav Petkov
2017-10-09 18:31 ` Andy Lutomirski
2017-10-13 9:07 ` demfloro
2017-10-14 10:49 ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
2017-10-14 12:34 ` [PATCH] x86/mm: Rip out the TLB benchmarking knob Borislav Petkov
2017-10-14 17:01 ` Andy Lutomirski
2017-10-14 16:34 ` [tip:x86/urgent] x86/mm: Flush more aggressively in lazy TLB mode Andy Lutomirski
2017-10-14 17:00 ` Andy Lutomirski
2017-10-16 2:39 ` [lkp-robot] [x86/mm] c4c3c3c2d0: will-it-scale.per_process_ops -61.0% regression kernel test robot
2017-10-16 2:39 ` kernel test robot
2017-10-16 10:15 ` Borislav Petkov
2017-10-16 10:15 ` Borislav Petkov
2017-10-17 1:06 ` Andy Lutomirski
2017-10-17 1:06 ` Andy Lutomirski
2017-10-17 4:57 ` Markus Trippelsdorf
2017-10-17 8:00 ` Borislav Petkov
2017-10-17 8:00 ` Borislav Petkov
2017-10-17 22:06 ` Andy Lutomirski
2017-10-17 22:06 ` Andy Lutomirski
2017-10-18 14:26 ` Borislav Petkov
2017-10-18 14:26 ` Borislav Petkov
2017-10-18 1:59 ` Ye Xiaolong
2017-10-18 1:59 ` Ye Xiaolong
2017-10-18 8:11 ` Borislav Petkov
2017-10-18 8:11 ` Borislav Petkov
2017-10-19 5:57 ` Ye Xiaolong [this message]
2017-10-17 6:04 ` Ye Xiaolong
2017-10-17 6:04 ` Ye Xiaolong
2017-10-10 8:22 ` [RFC PATCH] x86/mm: Flush more aggressively in lazy TLB mode Markus Trippelsdorf
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=20171019055725.GA22668@yexl-desktop \
--to=xiaolong.ye@intel.com \
--cc=lkp@lists.01.org \
/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.