From: Artem Bityutskiy <dedekind1@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org, mgorman@suse.de,
jhladky@redhat.com
Subject: Re: [PATCH] numa,sched: only consider less busy nodes as numa balancing destination
Date: Wed, 13 May 2015 13:59:50 +0300 [thread overview]
Message-ID: <1431514790.20417.18.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20150513062906.GJ3007@worktop.Skamania.guest>
On Wed, 2015-05-13 at 08:29 +0200, Peter Zijlstra wrote:
> > 2) ensure that rq->nr_numa_running and rq->nr_preferred_running also
> > get incremented for kernel threads that are bound to a particular
> > CPU - currently CPU-bound kernel threads will cause the NUMA
> > statistics to look like a CPU has tasks that do not belong on that
> > NUMA node
>
> I'm thinking accounting those to nr_pinned, lemme see how that works
> out.
Does not make any difference, avg. response time is still ~1.4sec.
Thank you!
next prev parent reply other threads:[~2015-05-13 10:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 10:35 autoNUMA web workload regression Artem Bityutskiy
2015-05-06 10:37 ` Bityutskiy, Artem
2015-05-06 14:40 ` Rik van Riel
2015-05-06 15:41 ` [PATCH] numa,sched: only consider less busy nodes as numa balancing destination Rik van Riel
2015-05-06 17:00 ` Peter Zijlstra
2015-05-06 17:06 ` Rik van Riel
2015-05-07 13:29 ` Artem Bityutskiy
2015-05-08 13:13 ` Artem Bityutskiy
2015-05-08 20:03 ` Rik van Riel
2015-05-08 22:52 ` Rik van Riel
2015-05-11 11:11 ` Artem Bityutskiy
2015-05-11 14:20 ` Rik van Riel
2015-05-12 13:50 ` Artem Bityutskiy
2015-05-12 15:45 ` Rik van Riel
2015-05-13 6:29 ` Peter Zijlstra
2015-05-13 6:31 ` Peter Zijlstra
2015-05-13 10:59 ` Artem Bityutskiy [this message]
2015-05-13 13:51 ` Rik van Riel
2015-05-11 12:44 ` Jirka Hladky
2015-05-11 14:44 ` Rik van Riel
2015-05-26 20:29 ` 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=1431514790.20417.18.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=jhladky@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=peterz@infradead.org \
--cc=riel@redhat.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
Powered by JetHome