From: Andy Whitcroft <apw@shadowen.org>
To: MinChan Kim <barrioskmc@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Peter Zijlstra <peterz@infradead.org>,
Christoph Lameter <cl@linux-foundation.org>,
Rik van Riel <riel@redhat.com>, Mel Gorman <mel@csn.ul.ie>
Subject: Re: [PATCH 1/4] pull out the page pre-release and sanity check logic for reuse
Date: Mon, 8 Sep 2008 16:14:13 +0100 [thread overview]
Message-ID: <20080908151413.GB9190@brain> (raw)
In-Reply-To: <44c63dc40809080711v98f4fdbs19081aa7cb81634d@mail.gmail.com>
On Mon, Sep 08, 2008 at 11:11:22PM +0900, MinChan Kim wrote:
> On Fri, Sep 5, 2008 at 7:19 PM, Andy Whitcroft <apw@shadowen.org> wrote:
> > When we are about to release a page we perform a number of actions
> > on that page. We clear down any anonymous mappings, confirm that
> > the page is safe to release, check for freeing locks, before mapping
> > the page should that be required. Pull this processing out into a
> > helper function for reuse in a later patch.
> >
> > Note that we do not convert the similar cleardown in free_hot_cold_page()
> > as the optimiser is unable to squash the loops during the inline.
> >
> > Signed-off-by: Andy Whitcroft <apw@shadowen.org>
> > Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > Acked-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> > Reviewed-by: Rik van Riel <riel@redhat.com>
> > ---
> > mm/page_alloc.c | 43 ++++++++++++++++++++++++++++++-------------
> > 1 files changed, 30 insertions(+), 13 deletions(-)
> >
> > diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> > index f52fcf1..b2a2c2b 100644
> > --- a/mm/page_alloc.c
> > +++ b/mm/page_alloc.c
> > @@ -489,6 +489,35 @@ static inline int free_pages_check(struct page *page)
> > }
> >
> > /*
> > + * Prepare this page for release to the buddy. Sanity check the page.
> > + * Returns 1 if the page is safe to free.
> > + */
> > +static inline int free_page_prepare(struct page *page, int order)
> > +{
> > + int i;
> > + int reserved = 0;
> > +
> > + if (PageAnon(page))
> > + page->mapping = NULL;
>
> Why do you need to clear down anonymous mapping ?
> I think if you don't convert this cleardown in free_hot_cold_page(),
> you don't need it.
>
> If you do it, bad_page can't do his role.
Yeah that has slipped through from where originally this patch used to
merge two different instances of this code. Good spot. Will sort that
out.
> > + for (i = 0 ; i < (1 << order) ; ++i)
> > + reserved += free_pages_check(page + i);
> > + if (reserved)
> > + return 0;
> > +
> > + if (!PageHighMem(page)) { > > + debug_check_no_locks_freed(page_address(page),
> > + PAGE_SIZE << order);
> > + debug_check_no_obj_freed(page_address(page),
> > + PAGE_SIZE << order);
> > + }
> > + arch_free_page(page, order);
> > + kernel_map_pages(page, 1 << order, 0);
> > +
> > + return 1;
> > +}
> > +
> > +/*
> > * Frees a list of pages.
> > * Assumes all pages on list are in same zone, and of same order.
> > * count is the number of pages to free.
> > @@ -529,22 +558,10 @@ static void free_one_page(struct zone *zone, struct page *page, int order)
> > static void __free_pages_ok(struct page *page, unsigned int order)
> > {
> > unsigned long flags;
> > - int i;
> > - int reserved = 0;
> >
> > - for (i = 0 ; i < (1 << order) ; ++i)
> > - reserved += free_pages_check(page + i);
> > - if (reserved)
> > + if (!free_page_prepare(page, order))
> > return;
> >
> > - if (!PageHighMem(page)) {
> > - debug_check_no_locks_freed(page_address(page),PAGE_SIZE<<order);
> > - debug_check_no_obj_freed(page_address(page),
> > - PAGE_SIZE << order);
> > - }
> > - arch_free_page(page, order);
> > - kernel_map_pages(page, 1 << order, 0);
> > -
> > local_irq_save(flags);
> > __count_vm_events(PGFREE, 1 << order);
> > free_one_page(page_zone(page), page, order);
-apw
--
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-08 15:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 10:19 [PATCH 0/4] Reclaim page capture v3 Andy Whitcroft
2008-09-05 10:19 ` [PATCH 1/4] pull out the page pre-release and sanity check logic for reuse Andy Whitcroft
2008-09-08 14:11 ` MinChan Kim
2008-09-08 15:14 ` Andy Whitcroft [this message]
2008-09-05 10:20 ` [PATCH 2/4] pull out zone cpuset and watermark checks " Andy Whitcroft
2008-09-05 10:20 ` [PATCH 3/4] buddy: explicitly identify buddy field use in struct page Andy Whitcroft
2008-09-05 10:20 ` [PATCH 4/4] capture pages freed during direct reclaim for allocation by the reclaimer Andy Whitcroft
2008-09-08 6:08 ` [PATCH 0/4] Reclaim page capture v3 Nick Piggin
2008-09-08 11:44 ` Andy Whitcroft
2008-09-08 13:59 ` Nick Piggin
2008-09-08 16:41 ` Andy Whitcroft
2008-09-09 3:31 ` Nick Piggin
2008-09-09 16:35 ` Andy Whitcroft
2008-09-10 3:19 ` Nick Piggin
2008-09-10 6:56 ` Andy Whitcroft
2008-09-12 21:30 ` Andy Whitcroft
-- 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:30 ` [PATCH 1/4] pull out the page pre-release and sanity check logic for reuse Andy Whitcroft
2008-10-02 7:05 ` KAMEZAWA Hiroyuki
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-07-01 17:58 [RFC PATCH 0/4] Reclaim page capture v1 Andy Whitcroft
2008-07-01 17:58 ` [PATCH 1/4] pull out the page pre-release and sanity check logic for reuse 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=20080908151413.GB9190@brain \
--to=apw@shadowen.org \
--cc=barrioskmc@gmail.com \
--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 \
--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