From: Rik van Riel <riel@surriel.com>
To: Mel Gorman <mgorman@techsingularity.net>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Linux-MM <linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched/numa: Avoid trapping faults and attempting migration of file-backed dirty pages
Date: Mon, 26 Mar 2018 17:59:24 -0400 [thread overview]
Message-ID: <1522101564.6308.61.camel@surriel.com> (raw)
In-Reply-To: <20180326094334.zserdec62gwmmfqf@techsingularity.net>
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
On Mon, 2018-03-26 at 10:43 +0100, Mel Gorman wrote:
> change_pte_range is called from task work context to mark PTEs for
> receiving
> NUMA faulting hints. If the marked pages are dirty then migration may
> fail.
> Some filesystems cannot migrate dirty pages without blocking so are
> skipped
> in MIGRATE_ASYNC mode which just wastes CPU. Even when they can, it
> can
> be a waste of cycles when the pages are shared forcing higher scan
> rates.
> Signed-off-by: Mel Gorman <mgorman@techsingularity.net>
Reviewed-by: Rik van Riel <riel@surriel.com>
--
All Rights Reversed.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-03-26 21:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 9:43 Mel Gorman
2018-03-26 21:59 ` Rik van Riel [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=1522101564.6308.61.camel@surriel.com \
--to=riel@surriel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
/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