public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
	mingo@kernel.org, mgorman@suse.de
Subject: Re: [PATCH] sched,numa: document and fix numa_preferred_nid setting
Date: Fri, 19 Jun 2015 13:52:27 -0400	[thread overview]
Message-ID: <558456DB.3040108@redhat.com> (raw)
In-Reply-To: <20150619171633.GC16576@linux.vnet.ibm.com>

On 06/19/2015 01:16 PM, Srikar Dronamraju wrote:
>>
>> OK, so we are looking at two multi-threaded processes
>> on a 4 node system, and waiting for them to converge?
>>
>> It may make sense to add my patch in with your patch
>> 1/4 from last week, as well as the correct part of
>> your patch 4/4, and see how they all work together.
>>
> 
> Tested specjbb and autonumabenchmark on 4 kernels.
> 
> Plain 4.1.0-rc7-tip (i)
> tip + only Rik's patch (ii)
> tip + Rik's ++ (iii)
> tip + Srikar's ++ (iv)

> 5 interations of Specjbb on 4 node, 24 core powerpc machine.
> Ran 1 instance per system.

Would you happen to have 2 instance and 4 instance SPECjbb
numbers, too?  The single instance numbers seem to be within
the margin of error, but I would expect multi-instance numbers
to show more dramatic changes, due to changes in how workloads
converge...

Those behave very differently from single instance, especially
with the "always set the preferred_nid, even if we moved the
task to a node we do NOT prefer" patch...

It would be good to understand the behaviour of these patches
under more circumstances.

-- 
All rights reversed
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2015-06-19 17:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 19:54 [PATCH] sched,numa: document and fix numa_preferred_nid setting Rik van Riel
2015-06-18 15:55 ` Srikar Dronamraju
2015-06-18 16:06   ` Rik van Riel
2015-06-18 16:41     ` Srikar Dronamraju
2015-06-18 17:00       ` Rik van Riel
2015-06-18 17:11         ` Srikar Dronamraju
2015-06-19 17:16         ` Srikar Dronamraju
2015-06-19 17:52           ` Rik van Riel [this message]
2015-06-22 16:04             ` Srikar Dronamraju
2015-06-22 16:48           ` Srikar Dronamraju
2015-06-18 16:12   ` Ingo Molnar
2015-06-18 18:16     ` Rik van Riel
2015-06-22 16:13 ` Srikar Dronamraju
2015-06-22 22:28   ` Rik van Riel

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=558456DB.3040108@redhat.com \
    --to=riel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=srikar@linux.vnet.ibm.com \
    /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