From: Huang, Ying <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [sched/idle] bb400b924e: fio.write_clat_95%_us -8% improvement
Date: Fri, 07 Apr 2017 14:02:38 +0800 [thread overview]
Message-ID: <87inmgah6p.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <070BEF4AC20468458C22969097656CD94BFB566F@shsmsx102.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 3882 bytes --]
"Li, Aubrey" <aubrey.li@intel.com> writes:
> Please help to take a look:
>
> aubrey(a)inn:~$ lkp queue -b aubrey-fast_idle/4.8.x -k
> ea899bd65fc285d5753d70a7879a7332821bbc02 -t lkp-bdw-ep2 job.yaml -r 3
> -q vip -e aubrey.li(a)intel.com
> aubrey(a)inn:~$ lkp wtmp lkp-bdw-ep2 | grep ea899
> aubrey(a)inn:~$ date
> Fri Apr 7 12:15:02 CST 2017
> aubrey(a)inn:~$ lkp wtmp lkp-bdw-ep2 | grep ea899
> aubrey(a)inn:~$ lkp wtmp lkp-bdw-ep2 | grep ea899
> aubrey(a)inn:~$ date
> Fri Apr 7 13:14:10 CST 2017
>
> I'm running as a VIP and one hour later, I still does not see my task being scheduled.
> Anything I did wrong or how to help it manually?
>
> Also, my last task took 10 hr total from scheduled to completion??
> http://bee.sh.intel.com:8080/job/lkp-aubrey-fast-idle/2/
> This is really unacceptable to me, please comment on the time cost.
I found your commit is not correct on inn,
$ cd /c/repo/linux
$ git show git show ea899bd65fc285d5753d70a7879a7332821bbc02
fatal: bad object ea899bd65fc285d5753d70a7879a7332821bbc02
Best Regards,
Huang, Ying
> Thanks,
> -Aubrey
>
>> -----Original Message-----
>> From: Huang, Ying
>> Sent: Friday, April 07, 2017 10:24 AM
>> To: Li, Aubrey
>> Cc: Ye, Xiaolong; Li, Aubrey; lkp(a)01.org; Huang, Ying; Du, Julie; Lu, LeiX
>> Subject: Re: [lkp-robot] [sched/idle] bb400b924e: fio.write_clat_95%_us -8%
>> improvement
>>
>> "Li, Aubrey" <aubrey.li@intel.com> writes:
>>
>> > On Friday, April 07, 2017 9:46 AM, Ye, Xiaolong wrote:
>> >>
>> >> >Can you point me a documentation how to do this?
>> >> >Or can you please show me the detailed steps?
>> >>
>> >> You may refer to lkp-core/doc/performance-work-guide.md.
>> >
>> > Thanks, I'll take a look.
>> >
>> >>
>> >> For simple use, you may
>> >>
>> >> 1) $ lkp queue -b stable/linux-4.8.y -k v4.8.8 -t lkp-bdw-ep2
>> >> job.yaml -r 3 (attached in the original mail or you can use any other
>> >> job.yaml customized)
>> >> 2) $ lkp queue -b fast_idle -k <your head commitid> -t lkp-bdw-ep2
>> >> job.yaml -r 3
>> >> 3) wait above jobs done, you can use `lkp wtmp lkp-bdw-ep2` to check
>> >> the progress
>> >> 4) $ lkp compare -at v4.8.8 <your head commitid> // it will show the
>> >> comparison
>> >>
>> >
>> > Does this guarantee there is no other task running simultaneously when
>> > my task is scheduled?
>>
>> Yes.
>>
>> >> >
>> >> Actually this is a bisect report, it bisected to the middle patch in your
>> patchset.
>> >> For the HEAD test result, it shares the same parent directory with
>> >> the bisected one, you can see it in
>> >> inn:/result/fio-basic/1SSD-btrfs-300s-8-randwrite-4k-sync-512g-perfor
>> >> mance/lkp
>> >> -bdw-ep2/debian-x86_64-2016-08-31.cgz/x86_64-rhel-7.2/gcc-6/<your
>> >> HEAD
>> >> commitid>
>> >>
>> >
>> > Is there a way not involving bisect process, what I want is
>> > benchmarking my kernel image and done, I really don't care which of my
>> > patch causes a difference, I just care if it's different against a
>> > BASE and I care the time, :)
>>
>> You can queue tests and compare the results by yourself. The bisect happens
>> in background, if you don't care the result, just ignore the result.
>>
>> Best Regards,
>> Huang, Ying
>>
>> >
>> >>
>> >> >
>> >> >> >
>> >> >> >(3) I need to dig into the test machine bios to confirm if it's
>> >> >> >compliant to my expected criteria, how to do that?
>> >> >> >
>> >> >>
>> >> >> The test machine is lkp-bdw-ep2, you may ssh into it to check?
>> >> >>
>> >> >
>> >> >ssh is not good enough to me. I need to change the BIOS setting.
>> >> >So I need KVM access (screen + keyboard) and root Privilege of that
>> >> >machine.
>> >>
>> >
>> >
>> >
>> >
>> >
>> >> +Lu Lei
>> >>
>> >> Hi, Lei
>> >>
>> >> Can you help on this?
>> >>
>> >
>> > Thanks,
>> > -Aubrey
next prev parent reply other threads:[~2017-04-07 6:02 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 7:12 [lkp-robot] [sched/idle] bb400b924e: fio.write_clat_95%_us -8% improvement kernel test robot
2017-04-06 5:56 ` Li, Aubrey
2017-04-06 6:26 ` Ye Xiaolong
2017-04-06 13:54 ` Li, Aubrey
2017-04-07 1:33 ` Huang, Ying
2017-04-07 1:47 ` Li, Aubrey
2017-04-07 2:21 ` Huang, Ying
2017-04-07 3:10 ` Li, Aubrey
2017-04-07 1:46 ` Ye Xiaolong
2017-04-07 2:12 ` Li, Aubrey
2017-04-07 2:24 ` Huang, Ying
2017-04-07 5:26 ` Li, Aubrey
2017-04-07 6:02 ` Huang, Ying [this message]
2017-04-07 6:06 ` Li, Aubrey
2017-04-07 6:11 ` Ye Xiaolong
2017-04-07 6:16 ` Li, Aubrey
2017-04-07 6:25 ` Huang, Ying
2017-04-07 6:41 ` Li, Aubrey
2017-04-07 6:44 ` Huang, Ying
2017-04-07 6:51 ` Li, Aubrey
2017-04-07 6:58 ` Huang, Ying
2017-04-07 6:12 ` Huang, Ying
2017-04-07 3:34 ` Li, Aubrey
2017-04-07 3:44 ` Ye Xiaolong
2017-04-07 6:58 ` Li, Aubrey
2017-04-07 7:03 ` Huang, Ying
2017-04-07 7:12 ` Li, Aubrey
2017-04-07 7:18 ` Huang, Ying
2017-04-07 8:32 ` Du, Julie
2017-04-07 8:39 ` Li, Aubrey
2017-04-07 8:43 ` Huang, Ying
2017-04-07 8:48 ` Li, Aubrey
2017-04-07 8:53 ` Li, Aubrey
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=87inmgah6p.fsf@yhuang-dev.intel.com \
--to=ying.huang@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.