From: Vlastimil Babka <vbabka@suse.cz>
To: David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Hugh Dickins <hughd@google.com>, Mel Gorman <mgorman@suse.de>,
Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch v2] mm, compaction: avoid isolating pinned pages
Date: Thu, 06 Feb 2014 19:48:50 +0100 [thread overview]
Message-ID: <52F3D912.4020607@suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.02.1402041842100.14045@chino.kir.corp.google.com>
On 5.2.2014 3:44, David Rientjes wrote:
> Page migration will fail for memory that is pinned in memory with, for
> example, get_user_pages(). In this case, it is unnecessary to take
> zone->lru_lock or isolating the page and passing it to page migration
> which will ultimately fail.
>
> This is a racy check, the page can still change from under us, but in
> that case we'll just fail later when attempting to move the page.
>
> This avoids very expensive memory compaction when faulting transparent
> hugepages after pinning a lot of memory with a Mellanox driver.
>
> On a 128GB machine and pinning ~120GB of memory, before this patch we
> see the enormous disparity in the number of page migration failures
> because of the pinning (from /proc/vmstat):
>
> compact_pages_moved 8450
> compact_pagemigrate_failed 15614415
>
> 0.05% of pages isolated are successfully migrated and explicitly
> triggering memory compaction takes 102 seconds. After the patch:
>
> compact_pages_moved 9197
> compact_pagemigrate_failed 7
>
> 99.9% of pages isolated are now successfully migrated in this
> configuration and memory compaction takes less than one second.
>
> Signed-off-by: David Rientjes <rientjes@google.com>
> ---
> v2: address page count issue per Joonsoo
>
> mm/compaction.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/mm/compaction.c b/mm/compaction.c
> --- a/mm/compaction.c
> +++ b/mm/compaction.c
> @@ -578,6 +578,15 @@ isolate_migratepages_range(struct zone *zone, struct compact_control *cc,
> continue;
> }
>
> + /*
> + * Migration will fail if an anonymous page is pinned in memory,
> + * so avoid taking lru_lock and isolating it unnecessarily in an
> + * admittedly racy check.
> + */
> + if (!page_mapping(page) &&
> + page_count(page) > page_mapcount(page))
> + continue;
> +
Hm this page_count() seems it could substantially increase the chance of
race with prep_compound_page that your patch "mm, page_alloc: make
first_page visible before PageTail" tries to fix :)
> /* Check if it is ok to still hold the lock */
> locked = compact_checklock_irqsave(&zone->lru_lock, &flags,
> locked, cc);
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Vlastimil Babka <vbabka@suse.cz>
To: David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Hugh Dickins <hughd@google.com>, Mel Gorman <mgorman@suse.de>,
Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch v2] mm, compaction: avoid isolating pinned pages
Date: Thu, 06 Feb 2014 19:48:50 +0100 [thread overview]
Message-ID: <52F3D912.4020607@suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.02.1402041842100.14045@chino.kir.corp.google.com>
On 5.2.2014 3:44, David Rientjes wrote:
> Page migration will fail for memory that is pinned in memory with, for
> example, get_user_pages(). In this case, it is unnecessary to take
> zone->lru_lock or isolating the page and passing it to page migration
> which will ultimately fail.
>
> This is a racy check, the page can still change from under us, but in
> that case we'll just fail later when attempting to move the page.
>
> This avoids very expensive memory compaction when faulting transparent
> hugepages after pinning a lot of memory with a Mellanox driver.
>
> On a 128GB machine and pinning ~120GB of memory, before this patch we
> see the enormous disparity in the number of page migration failures
> because of the pinning (from /proc/vmstat):
>
> compact_pages_moved 8450
> compact_pagemigrate_failed 15614415
>
> 0.05% of pages isolated are successfully migrated and explicitly
> triggering memory compaction takes 102 seconds. After the patch:
>
> compact_pages_moved 9197
> compact_pagemigrate_failed 7
>
> 99.9% of pages isolated are now successfully migrated in this
> configuration and memory compaction takes less than one second.
>
> Signed-off-by: David Rientjes <rientjes@google.com>
> ---
> v2: address page count issue per Joonsoo
>
> mm/compaction.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/mm/compaction.c b/mm/compaction.c
> --- a/mm/compaction.c
> +++ b/mm/compaction.c
> @@ -578,6 +578,15 @@ isolate_migratepages_range(struct zone *zone, struct compact_control *cc,
> continue;
> }
>
> + /*
> + * Migration will fail if an anonymous page is pinned in memory,
> + * so avoid taking lru_lock and isolating it unnecessarily in an
> + * admittedly racy check.
> + */
> + if (!page_mapping(page) &&
> + page_count(page) > page_mapcount(page))
> + continue;
> +
Hm this page_count() seems it could substantially increase the chance of
race with prep_compound_page that your patch "mm, page_alloc: make
first_page visible before PageTail" tries to fix :)
> /* Check if it is ok to still hold the lock */
> locked = compact_checklock_irqsave(&zone->lru_lock, &flags,
> locked, cc);
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-02-06 23:04 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 5:46 [patch] mm, compaction: avoid isolating pinned pages David Rientjes
2014-02-02 5:46 ` David Rientjes
2014-02-03 9:53 ` Mel Gorman
2014-02-03 9:53 ` Mel Gorman
2014-02-03 10:49 ` David Rientjes
2014-02-03 10:49 ` David Rientjes
2014-02-04 0:02 ` Joonsoo Kim
2014-02-04 0:02 ` Joonsoo Kim
2014-02-04 1:20 ` [patch] mm, compaction: avoid isolating pinned pages fix David Rientjes
2014-02-04 1:20 ` David Rientjes
2014-02-04 1:53 ` Joonsoo Kim
2014-02-04 1:53 ` Joonsoo Kim
2014-02-04 2:00 ` David Rientjes
2014-02-04 2:00 ` David Rientjes
2014-02-04 2:15 ` Joonsoo Kim
2014-02-04 2:15 ` Joonsoo Kim
2014-02-04 2:50 ` David Rientjes
2014-02-04 2:50 ` David Rientjes
2014-02-04 3:47 ` Hugh Dickins
2014-02-04 3:47 ` Hugh Dickins
2014-02-05 2:44 ` [patch v2] mm, compaction: avoid isolating pinned pages David Rientjes
2014-02-05 2:44 ` David Rientjes
2014-02-05 20:56 ` Hugh Dickins
2014-02-05 20:56 ` Hugh Dickins
2014-02-06 0:05 ` Joonsoo Kim
2014-02-06 0:05 ` Joonsoo Kim
2014-02-06 1:16 ` Hugh Dickins
2014-02-06 1:16 ` Hugh Dickins
2014-02-06 13:53 ` Mel Gorman
2014-02-06 13:53 ` Mel Gorman
2014-02-06 18:48 ` Vlastimil Babka [this message]
2014-02-06 18:48 ` Vlastimil Babka
2014-02-06 21:33 ` David Rientjes
2014-02-06 21:33 ` David Rientjes
2014-02-04 2:44 ` [patch] " Hugh Dickins
2014-02-04 2:44 ` Hugh Dickins
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=52F3D912.4020607@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=riel@redhat.com \
--cc=rientjes@google.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.