From: Peter Zijlstra <peterz@infradead.org>
To: Andy Whitcroft <apw@shadowen.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Mel Gorman <mel@csn.ul.ie>,
Christoph Lameter <cl@linux-foundation.org>
Subject: Re: [PATCH 4/4] capture pages freed during direct reclaim for allocation by the reclaimer
Date: Thu, 04 Sep 2008 09:20:18 +0200 [thread overview]
Message-ID: <1220512818.8609.174.camel@twins> (raw)
In-Reply-To: <1220475206-23684-1-git-send-email-apw@shadowen.org>
On Wed, 2008-09-03 at 21:53 +0100, Andy Whitcroft wrote:
> [Doh, as pointed out by Christoph the patch was missing from this one...]
>
> When a process enters direct reclaim it will expend effort identifying
> and releasing pages in the hope of obtaining a page. However as these
> pages are released asynchronously there is every possibility that the
> pages will have been consumed by other allocators before the reclaimer
> gets a look in. This is particularly problematic where the reclaimer is
> attempting to allocate a higher order page. It is highly likely that
> a parallel allocation will consume lower order constituent pages as we
> release them preventing them coelescing into the higher order page the
> reclaimer desires.
>
> This patch set attempts to address this for allocations above
> ALLOC_COSTLY_ORDER by temporarily collecting the pages we are releasing
> onto a local free list. Instead of freeing them to the main buddy lists,
> pages are collected and coelesced on this per direct reclaimer free list.
> Pages which are freed by other processes are also considered, where they
> coelesce with a page already under capture they will be moved to the
> capture list. When pressure has been applied to a zone we then consult
> the capture list and if there is an appropriatly sized page available
> it is taken immediatly and the remainder returned to the free pool.
> Capture is only enabled when the reclaimer's allocation order exceeds
> ALLOC_COSTLY_ORDER as free pages below this order should naturally occur
> in large numbers following regular reclaim.
>
> Thanks go to Mel Gorman for numerous discussions during the development
> of this patch and for his repeated reviews.
Whole series looks good, a few comments below.
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Signed-off-by: Andy Whitcroft <apw@shadowen.org>
> ---
> @@ -4815,6 +4900,73 @@ out:
> spin_unlock_irqrestore(&zone->lock, flags);
> }
>
> +#define lru_to_page(_head) (list_entry((_head)->prev, struct page, lru))
> +
> +/*
> + * Run through the accumulated list of captured pages and the first
> + * which is big enough to satisfy the original allocation. Free
> + * the remainder of that page and all other pages.
> + */
That sentence looks incomplete, did you intend to write something along
the lines of:
Run through the accumulated list of captures pages and /take/ the first
which is big enough to satisfy the original allocation. Free the
remaining pages.
?
> +struct page *capture_alloc_or_return(struct zone *zone,
> + struct zone *preferred_zone, struct list_head *capture_list,
> + int order, int alloc_flags, gfp_t gfp_mask)
> +{
> + struct page *capture_page = 0;
> + unsigned long flags;
> + int classzone_idx = zone_idx(preferred_zone);
> +
> + spin_lock_irqsave(&zone->lock, flags);
> +
> + while (!list_empty(capture_list)) {
> + struct page *page;
> + int pg_order;
> +
> + page = lru_to_page(capture_list);
> + list_del(&page->lru);
> + pg_order = page_order(page);
> +
> + /*
> + * Clear out our buddy size and list information before
> + * releasing or allocating the page.
> + */
> + rmv_page_order(page);
> + page->buddy_free = 0;
> + ClearPageBuddyCapture(page);
> +
> + if (!capture_page && pg_order >= order) {
> + __carve_off(page, pg_order, order);
> + capture_page = page;
> + } else
> + __free_one_page(page, zone, pg_order);
> + }
> +
> + /*
> + * Ensure that this capture would not violate the watermarks.
> + * Subtle, we actually already have the page outside the watermarks
> + * so check if we can allocate an order 0 page.
> + */
> + if (capture_page &&
> + (!zone_cpuset_permits(zone, alloc_flags, gfp_mask) ||
> + !zone_watermark_permits(zone, 0, classzone_idx,
> + alloc_flags, gfp_mask))) {
> + __free_one_page(capture_page, zone, order);
> + capture_page = NULL;
> + }
This makes me a little sad - we got a high order page and give it away
again...
Can we start another round of direct reclaim with a lower order to try
and increase the watermarks while we hold on to this large order page?
> + if (capture_page)
> + __count_zone_vm_events(PGALLOC, zone, 1 << order);
> +
> + zone_clear_flag(zone, ZONE_ALL_UNRECLAIMABLE);
> + zone->pages_scanned = 0;
> +
> + spin_unlock_irqrestore(&zone->lock, flags);
> +
> + if (capture_page)
> + prep_new_page(capture_page, order, gfp_mask);
> +
> + return capture_page;
> +}
> +
> #ifdef CONFIG_MEMORY_HOTREMOVE
> /*
> * All pages in the range must be isolated before calling this.
--
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:[~2008-09-04 7:20 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 18:44 [RFC PATCH 0/4] Reclaim page capture v2 Andy Whitcroft
2008-09-03 18:44 ` [PATCH 1/4] pull out the page pre-release and sanity check logic for reuse Andy Whitcroft
2008-09-04 1:24 ` Rik van Riel
2008-09-05 1:52 ` KOSAKI Motohiro
2008-09-03 18:44 ` [PATCH 2/4] pull out zone cpuset and watermark checks " Andy Whitcroft
2008-09-04 1:24 ` Rik van Riel
2008-09-05 1:52 ` KOSAKI Motohiro
2008-09-03 18:44 ` [PATCH 3/4] buddy: explicitly identify buddy field use in struct page Andy Whitcroft
2008-09-03 20:36 ` Christoph Lameter
2008-09-04 1:25 ` Rik van Riel
2008-09-05 1:52 ` KOSAKI Motohiro
2008-09-03 18:44 ` [PATCH 4/4] capture pages freed during direct reclaim for allocation by the reclaimer Andy Whitcroft
2008-09-03 20:35 ` Christoph Lameter
2008-09-03 20:53 ` Andy Whitcroft
2008-09-03 21:00 ` Christoph Lameter
2008-09-04 6:38 ` Peter Zijlstra
2008-09-04 14:18 ` Christoph Lameter
2008-09-04 8:11 ` KOSAKI Motohiro
2008-09-04 8:58 ` Andy Whitcroft
2008-09-04 7:20 ` Peter Zijlstra [this message]
2008-09-04 11:35 ` Andy Whitcroft
2008-09-04 7:59 ` KOSAKI Motohiro
2008-09-04 14:44 ` Andy Whitcroft
2008-09-05 1:52 ` KOSAKI Motohiro
-- strict thread matches above, loose matches on Subject: below --
2008-10-01 12:30 [PATCH 0/4] Reclaim page capture v4 Andy Whitcroft
2008-10-01 12:31 ` [PATCH 4/4] capture pages freed during direct reclaim for allocation by the reclaimer Andy Whitcroft
2008-10-01 15:01 ` Christoph Lameter
2008-10-02 14:35 ` Andy Whitcroft
2008-10-02 16:29 ` Christoph Lameter
2008-10-03 3:41 ` KOSAKI Motohiro
2008-10-03 12:37 ` Christoph Lameter
2008-10-02 7:24 ` KAMEZAWA Hiroyuki
2008-10-02 15:02 ` Andy Whitcroft
2008-09-05 10:19 [PATCH 0/4] Reclaim page capture v3 Andy Whitcroft
2008-09-05 10:20 ` [PATCH 4/4] capture pages freed during direct reclaim for allocation by the reclaimer Andy Whitcroft
2008-07-01 17:58 [RFC PATCH 0/4] Reclaim page capture v1 Andy Whitcroft
2008-07-01 17:58 ` [PATCH 4/4] capture pages freed during direct reclaim for allocation by the reclaimer Andy Whitcroft
2008-07-02 12:01 ` KOSAKI Motohiro
2008-07-02 14:44 ` Andy Whitcroft
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=1220512818.8609.174.camel@twins \
--to=peterz@infradead.org \
--cc=apw@shadowen.org \
--cc=cl@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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