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: Thu, 18 Jun 2015 13:00:52 -0400 [thread overview]
Message-ID: <5582F944.6080204@redhat.com> (raw)
In-Reply-To: <20150618164140.GB16576@linux.vnet.ibm.com>
On 06/18/2015 12:41 PM, Srikar Dronamraju wrote:
> * Rik van Riel <riel@redhat.com> [2015-06-18 12:06:49]:
>
>>>>
>>>
>>> Overall this patch does seem to produce better results. However numa02
>>> gets affected -vely.
>>
>> OK, that is kind of expected.
>>
>> The way numa02 runs means that we are essentially guaranteed
>> that, on a two node system, both nodes end up in the numa_group's
>> active_mask.
>>
>
> Just to add this was on a 4 node machine.
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.
next prev parent reply other threads:[~2015-06-18 17:01 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 [this message]
2015-06-18 17:11 ` Srikar Dronamraju
2015-06-19 17:16 ` Srikar Dronamraju
2015-06-19 17:52 ` Rik van Riel
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=5582F944.6080204@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 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.