From: Mel Gorman <mgorman@suse.de>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: linux-mm@kvack.org, Kyungmin Park <kyungmin.park@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH][RFC] mm: compaction: handle incorrect Unmovable type pageblocks
Date: Thu, 26 Apr 2012 10:06:43 +0100 [thread overview]
Message-ID: <20120426090643.GE15299@suse.de> (raw)
In-Reply-To: <201204241403.29860.b.zolnierkie@samsung.com>
On Tue, Apr 24, 2012 at 02:03:29PM +0200, Bartlomiej Zolnierkiewicz wrote:
> > > include/linux/mmzone.h | 10 ++
> > > mm/compaction.c | 3
> > > mm/internal.h | 1
> > > mm/page_alloc.c | 128 +++++++++++++++++++++++++++++
> > > mm/sparse.c | 216 +++++++++++++++++++++++++++++++++++++++++++++++--
> > > 5 files changed, 353 insertions(+), 5 deletions(-)
> > >
> > > Index: b/include/linux/mmzone.h
> > > ===================================================================
> > > --- a/include/linux/mmzone.h 2012-04-20 16:35:16.894872193 +0200
> > > +++ b/include/linux/mmzone.h 2012-04-23 09:55:01.845549009 +0200
> > > @@ -379,6 +379,10 @@
> > > * In SPARSEMEM, this map is stored in struct mem_section
> > > */
> > > unsigned long *pageblock_flags;
> > > +
> > > +#ifdef CONFIG_COMPACTION
> > > + unsigned long *unmovable_map;
> > > +#endif
> > > #endif /* CONFIG_SPARSEMEM */
> > >
> > > #ifdef CONFIG_COMPACTION
> > > @@ -1033,6 +1037,12 @@
> > >
> > > /* See declaration of similar field in struct zone */
> > > unsigned long *pageblock_flags;
> > > +
> > > +#ifdef CONFIG_COMPACTION
> > > + unsigned long *unmovable_map;
> > > + unsigned long pad0; /* Why this is needed? */
> > > +#endif
> > > +
> >
> > You tell us, you added the padding :)
>
> I wish I could.. :)
>
> > If I had to guess you are trying to avoid sharing a cache line between
> > unmovable_map and adjacent fields but I doubt it is necessary.
>
> Unfortunately the pad is needed or the kernel just freezes somewhere
> early during memory zone initialization. I don't remember details but
> it was somewhere on the access to page->flags of the first page..
>
Sounds like it was a bug in how the bitmask was managed. It's not worth
losing sleep over as I expect the bitmap is removed by now.
> > > #ifdef CONFIG_CGROUP_MEM_RES_CTLR
> > > /*
> > > * If !SPARSEMEM, pgdat doesn't have page_cgroup pointer. We use
> > > Index: b/mm/compaction.c
> > > ===================================================================
> > > --- a/mm/compaction.c 2012-04-20 16:35:16.910872188 +0200
> > > +++ b/mm/compaction.c 2012-04-23 09:33:54.525527592 +0200
> > > @@ -376,6 +376,9 @@
> > > if (migrate_async_suitable(migratetype))
> > > return true;
> > >
> > > + if (migratetype == MIGRATE_UNMOVABLE && set_unmovable_movable(page))
> > > + return true;
> > > +
> >
> > Ok, I have a two suggested changes to this
> >
> > 1. compaction currently has sync and async compaction. I suggest you
> > make it a three states called async_partial, async_full and sync.
> > async_partial would be the current behaviour. async_full and sync
> > would both scan within MIGRATE_UNMOVABLE blocks to see if they
> > needed to be changed. This will add a new slower path but the
> > common path will be as it is today.
> >
> > 2. You maintain a bitmap of unmovable pages. Get rid of it. Instead have
> > set_unmovable_movable scan the pageblock and build a free count based
> > on finding PageBuddy pages, page_count(page) == 0 or PageLRU pages.
> > If all pages within the block are in one of those three sets, call
> > set_pageblock_migratetype(MIGRATE_MOVABLE) and call move_freepages_block()
> > I also suggest finding a better name than set_unmovable_movable
> > although I do not have a better suggestion myself right now.
>
> Ok, I'll post the updated patch shortly.
>
I'll review this ASAP.
--
Mel Gorman
SUSE Labs
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-04-26 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201204231202.55739.b.zolnierkie@samsung.com>
2012-04-23 14:56 ` [PATCH][RFC] mm: compaction: handle incorrect Unmovable type pageblocks Mel Gorman
2012-04-24 12:03 ` Bartlomiej Zolnierkiewicz
2012-04-26 9:06 ` Mel Gorman [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=20120426090643.GE15299@suse.de \
--to=mgorman@suse.de \
--cc=b.zolnierkie@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.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;
as well as URLs for NNTP newsgroup(s).