linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yuyang Du <yuyang.du@intel.com>
To: Boqun Feng <boqun.feng@gmail.com>
Cc: mingo@kernel.org, peterz@infradead.org,
	linux-kernel@vger.kernel.org, pjt@google.com, bsegall@google.com,
	morten.rasmussen@arm.com, vincent.guittot@linaro.org,
	dietmar.eggemann@arm.com, arjan.van.de.ven@intel.com,
	len.brown@intel.com, rafael.j.wysocki@intel.com,
	fengguang.wu@intel.com,
	Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Subject: Re: [PATCH v8 0/4] sched: Rewrite runnable load and utilization average tracking
Date: Tue, 16 Jun 2015 02:46:27 +0800	[thread overview]
Message-ID: <20150615184627.GA1244@intel.com> (raw)
In-Reply-To: <20150615103856.GA9722@fixme-laptop.cn.ibm.com>

Hi Boqun,

Thanks for the tests.

Indeed I can't find the 8th versio myself in the archive. That is weird.
Vincent sure received the patches, but maybe not the list, then that is
interesting...

Anyway, I will rebase the patches up-to-date, and resend it to the list
shortly.

Regarding test results, "less than 50% sometimes" meaning imbalanced?
What about versus the stock kernel?

Regards,
Yuyang

On Mon, Jun 15, 2015 at 06:38:56PM +0800, Boqun Feng wrote:
> Hi Yuyang,
> 
> We have tested your V7 patchset as follow:
> 
> On Intel(R) Xeon(R) CPU X5690 (12 cores), run 12 stress and 6 dbench.
> Results show that usages of some CPUs are less than 50% sometimes.
> 
> We would like to test your V8 patchset, but I can neither find it in a
> lkml archive, nor in my lkml subscription. Would you please send me your
> V8 patchset, if convenient? Or a public git tree works too!
> 
> Regards,
> Boqun
> 
> On Tue, Jun 09, 2015 at 09:21:43AM +0800, Yuyang Du wrote:
> > Ping ...
> > 
> > Plus some data tested by LKP:
> > 
> > To name a few host configurations:
> > 
> > host: brickland3
> > model: Brickland Ivy Bridge-EX
> > nr_cpu: 120
> > memory: 512G
> > 
> > host: lkp-a03
> > model: Atom
> > memory: 8G
> > 
> > host: grantley
> > model: Grantley Haswell-EP
> > memory: 32G
> > 
> > host: ivb43
> > model: Ivytown Ivy Bridge-EP
> > nr_cpu: 48
> > memory: 64G
> > 
> [snip]



      reply	other threads:[~2015-06-16  2:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1432518587-114210-1-git-send-email-yuyang.du@intel.com>
     [not found] ` <1432518587-114210-3-git-send-email-yuyang.du@intel.com>
2015-05-26 16:06   ` [PATCH v8 2/4] sched: Rewrite runnable load and utilization average tracking Vincent Guittot
2015-05-27 22:36     ` Yuyang Du
2015-06-02  0:25 ` [PATCH v8 0/4] " Yuyang Du
2015-06-09  1:21 ` Yuyang Du
2015-06-15 10:38   ` Boqun Feng
2015-06-15 18:46     ` Yuyang Du [this message]

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=20150615184627.GA1244@intel.com \
    --to=yuyang.du@intel.com \
    --cc=arjan.van.de.ven@intel.com \
    --cc=boqun.feng@gmail.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=fengguang.wu@intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=morten.rasmussen@arm.com \
    --cc=peterz@infradead.org \
    --cc=pjt@google.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=srikar@linux.vnet.ibm.com \
    --cc=vincent.guittot@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).