From: Mel Gorman <mgorman@suse.de>
To: riel@redhat.com
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@kernel.org, jhladky@redhat.com, lvenanci@redhat.com
Subject: Re: [RHEL-ALT-7.4 PATCH 1/2] numa,sched: slow down scan rate if shared faults dominate
Date: Wed, 2 Aug 2017 08:01:39 +0100 [thread overview]
Message-ID: <20170802070139.qsfo5ydcafdlomso@suse.de> (raw)
In-Reply-To: <20170731192847.23050-2-riel@redhat.com>
On Mon, Jul 31, 2017 at 03:28:46PM -0400, Rik van Riel wrote:
> From: Rik van Riel <riel@redhat.com>
>
> The comment above update_task_scan_period says the scan period should
> be increased (scanning slows down) if the majority of memory accesses
> are on the local node, or if the majority of the page accesses are
> shared with other tasks.
>
> However, with the current code, all a high ratio of shared accesses
> does is slow down the rate at which scanning is made faster.
>
> This patch changes things so either lots of shared accesses or
> lots of local accesses will slow down scanning, and numa scanning
> is sped up only when there are lots of private faults on remote
> memory pages.
>
> Signed-off-by: Rik van Riel <riel@redhat.com>
Acked-by: Mel Gorman <mgorman@suse.de>
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2017-08-02 7:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 19:28 [PATCH 0/2] numa,sched: improve performance for multi-threaded workloads riel
2017-07-31 19:28 ` [RHEL-ALT-7.4 PATCH 1/2] numa,sched: slow down scan rate if shared faults dominate riel
2017-08-02 7:01 ` Mel Gorman [this message]
2017-08-10 12:07 ` [tip:sched/core] sched/numa: Slow " tip-bot for Rik van Riel
2017-07-31 19:28 ` [RHEL-ALT-7.4 PATCH 2/2] sched,numa: scale scan period with tasks in group and shared/private riel
2017-08-02 10:22 ` Mel Gorman
2017-08-10 12:07 ` [tip:sched/core] sched/numa: Scale " tip-bot for 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=20170802070139.qsfo5ydcafdlomso@suse.de \
--to=mgorman@suse.de \
--cc=jhladky@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lvenanci@redhat.com \
--cc=mingo@kernel.org \
--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