All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Shi <alex.shi@linaro.org>
To: lkp@lists.01.org
Subject: Re: [sched/balance] 18e6296b85e: -96.9% interrupts.RES
Date: Tue, 04 Mar 2014 23:32:19 +0800	[thread overview]
Message-ID: <5315F203.80602@linaro.org> (raw)
In-Reply-To: <20140304130559.GA28781@localhost>

[-- Attachment #1: Type: text/plain, Size: 2187 bytes --]

Thanks a lot for the testing result!

I know the problem I have. :)


On 03/04/2014 09:05 PM, Fengguang Wu wrote:
> Hi Alex,
>
> FYI, we noticed the below changes on
>
> https://github.com/alexshi/power-scheduling.git single-balance
> commit 18e6296b85ea72c81aa485653d442ad88296d475 ("sched/balance: central balance prototype")
>
> test case: snb-drag/crypto/tcrypt/2s-301-319
>
> 598143917dc5ecf  18e6296b85ea72c81aa485653
> ---------------  -------------------------
>      206307 ~ 0%     -96.9%       6337 ~ 4%  TOTAL interrupts.RES
>      506552 ~ 1%     -24.3%     383290 ~ 3%  TOTAL cpuidle.C6-SNB.usage
>       18.27 ~ 9%   +1063.5%     212.53 ~25%  TOTAL time.system_time
>           1 ~30%   +1262.5%         21 ~31%  TOTAL time.percent_of_cpu_this_job_got
>         821 ~12%     -22.3%        638 ~19%  TOTAL vmstat.system.in
>
>
>
>                                   time.system_time
>
>     400 ++-------------------------------------------------------------------+
>         |                                                                    |
>     350 ++        O         O    O                                           |
>     300 ++O  O                     O                                         |
>         O      O         O    O       O O                                    |
>     250 ++          O                          O                             |
>         |              O                          O                          |
>     200 ++                                                                   |
>         |                                  O                                 |
>     150 ++                                   O                               |
>     100 ++                                                                   |
>         |                                                                    |
>      50 ++                                                                   |
>         *.*..*.*..*.*..*.*..*.*..*.*..*.*..*.*.*..*.*..*.*..*.*..*.*..*.*..*.*
>       0 ++-------------------------------------------------------------------+
>
>
> Thanks,
> Fengguang


WARNING: multiple messages have this Message-ID (diff)
From: Alex Shi <alex.shi@linaro.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>, lkp@01.org
Subject: Re: [sched/balance] 18e6296b85e: -96.9% interrupts.RES
Date: Tue, 04 Mar 2014 23:32:19 +0800	[thread overview]
Message-ID: <5315F203.80602@linaro.org> (raw)
In-Reply-To: <20140304130559.GA28781@localhost>

Thanks a lot for the testing result!

I know the problem I have. :)


On 03/04/2014 09:05 PM, Fengguang Wu wrote:
> Hi Alex,
>
> FYI, we noticed the below changes on
>
> https://github.com/alexshi/power-scheduling.git single-balance
> commit 18e6296b85ea72c81aa485653d442ad88296d475 ("sched/balance: central balance prototype")
>
> test case: snb-drag/crypto/tcrypt/2s-301-319
>
> 598143917dc5ecf  18e6296b85ea72c81aa485653
> ---------------  -------------------------
>      206307 ~ 0%     -96.9%       6337 ~ 4%  TOTAL interrupts.RES
>      506552 ~ 1%     -24.3%     383290 ~ 3%  TOTAL cpuidle.C6-SNB.usage
>       18.27 ~ 9%   +1063.5%     212.53 ~25%  TOTAL time.system_time
>           1 ~30%   +1262.5%         21 ~31%  TOTAL time.percent_of_cpu_this_job_got
>         821 ~12%     -22.3%        638 ~19%  TOTAL vmstat.system.in
>
>
>
>                                   time.system_time
>
>     400 ++-------------------------------------------------------------------+
>         |                                                                    |
>     350 ++        O         O    O                                           |
>     300 ++O  O                     O                                         |
>         O      O         O    O       O O                                    |
>     250 ++          O                          O                             |
>         |              O                          O                          |
>     200 ++                                                                   |
>         |                                  O                                 |
>     150 ++                                   O                               |
>     100 ++                                                                   |
>         |                                                                    |
>      50 ++                                                                   |
>         *.*..*.*..*.*..*.*..*.*..*.*..*.*..*.*.*..*.*..*.*..*.*..*.*..*.*..*.*
>       0 ++-------------------------------------------------------------------+
>
>
> Thanks,
> Fengguang


  reply	other threads:[~2014-03-04 15:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 13:05 [sched/balance] 18e6296b85e: -96.9% interrupts.RES Fengguang Wu
2014-03-04 13:05 ` Fengguang Wu
2014-03-04 15:32 ` Alex Shi [this message]
2014-03-04 15:32   ` Alex Shi

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=5315F203.80602@linaro.org \
    --to=alex.shi@linaro.org \
    --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.