All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jet Chen <jet.chen@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Kirill Tkhai <ktkhai@parallels.com>,
	Juri Lelli <juri.lelli@gmail.com>,
	Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [sched/idle] c365c292d05: ltp.sched_rr_get_interval02.1.TFAIL
Date: Fri, 07 Mar 2014 19:32:25 +0800	[thread overview]
Message-ID: <5319AE49.2000606@intel.com> (raw)

Hi Peter,

> Does: http://lkml.kernel.org/r/20140301191838.d15d03112b2598a671dac22c@gmail.com
>
> Fix it?

Both patches can fix the LTP regression.

We applied each of Juri's and Kirill's patches on top of Thomas' commit,
and here are the comparisons:

test case: ltp/syscalls

Thomas'          Juri's
c365c292d05908c  ffc78ca31d51f90c516bb50cf
---------------  -------------------------
         1 ~ 0%    -100.0%          0 ~ 0%  TOTAL ltp.sched_rr_get_interval02.1.TFAIL
     73790 ~ 5%     -14.1%      63363 ~ 6%  TOTAL interrupts.IWI
      3040 ~ 4%      -6.7%       2836 ~ 5%  TOTAL slabinfo.kmalloc-128.num_objs

Thomas'          Kirill's
c365c292d05908c  f4262311faf6f326bf27fb1f4
---------------  -------------------------
         1 ~ 0%    -100.0%          0 ~ 0%  TOTAL ltp.sched_rr_get_interval02.1.TFAIL
      3618 ~ 6%     -13.2%       3141 ~ 6%  TOTAL slabinfo.anon_vma.active_objs
      3671 ~ 5%     -11.3%       3258 ~ 4%  TOTAL slabinfo.anon_vma.num_objs
      8.41 ~ 2%      -5.1%       7.98 ~ 3%  TOTAL boottime.dhcp
     15.90 ~ 2%      -3.2%      15.40 ~ 2%  TOTAL boottime.boot
     55.18 ~ 1%      -2.6%      53.73 ~ 1%  TOTAL boottime.idle

Thanks,
-Jet


             reply	other threads:[~2014-03-07 11:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07 11:32 Jet Chen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-03-05  1:51 [sched/idle] c365c292d05: ltp.sched_rr_get_interval02.1.TFAIL Fengguang Wu
2014-03-05  1:51 ` Fengguang Wu
2014-03-05 11:02 ` Peter Zijlstra
2014-03-05 11:02   ` Peter Zijlstra

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=5319AE49.2000606@intel.com \
    --to=jet.chen@intel.com \
    --cc=20140305110238.GS9987@twins.programming.kicks-ass.net \
    --cc=fengguang.wu@intel.com \
    --cc=juri.lelli@gmail.com \
    --cc=ktkhai@parallels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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.