From: mel@skynet.ie (Mel Gorman)
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Lameter <clameter@sgi.com>,
linux-mm@kvack.org, hugh@veritas.com
Subject: Re: Fix page allocation flags in grow_dev_page()
Date: Wed, 16 May 2007 22:48:57 +0100 [thread overview]
Message-ID: <20070516214856.GA1718@skynet.ie> (raw)
In-Reply-To: <20070516133416.9d730d08.akpm@linux-foundation.org>
On (16/05/07 13:34), Andrew Morton didst pronounce:
> On Tue, 15 May 2007 21:12:41 -0700 (PDT)
> Christoph Lameter <clameter@sgi.com> wrote:
>
> > Grow dev page simply passes GFP_NOFS to find_or_create_page. This means the
> > allocation of radix tree nodes is done with GFP_NOFS and the allocation
> > of a new page is done using GFP_NOFS.
> >
> > The mapping has a flags field that contains the necessary allocation flags for
> > the page cache allocation. These need to be consulted in order to get DMA
> > and HIGHMEM allocations etc right. And yes a blockdev could be allowing
> > Highmem allocations if its a ramdisk.
> >
> > Cc: Hugh Dickins <hugh@veritas.com>
> > Signed-off-by: Christoph Lameter <clameter@sgi.com>
> >
> > ---
> > fs/buffer.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > Index: vps/fs/buffer.c
> > ===================================================================
> > --- vps.orig/fs/buffer.c 2007-05-15 15:47:32.000000000 -0700
> > +++ vps/fs/buffer.c 2007-05-15 15:48:36.000000000 -0700
> > @@ -981,7 +981,8 @@ grow_dev_page(struct block_device *bdev,
> > struct page *page;
> > struct buffer_head *bh;
> >
> > - page = find_or_create_page(inode->i_mapping, index, GFP_NOFS);
> > + page = find_or_create_page(inode->i_mapping, index,
> > + mapping_gfp_mask(inode->i_mapping) & ~__GFP_FS);
> > if (!page)
> > return NULL;
> >
>
> erk. When I fixed this up against Mel's stuff I ended up with:
>
> page = find_or_create_page(inode->i_mapping, index,
> (mapping_gfp_mask(inode->i_mapping) & ~__GFP_FS) |
> __GFP_RECLAIMABLE);
>
> which led to zillions of these:
>
> static inline int allocflags_to_migratetype(gfp_t gfp_flags)
> {
> WARN_ON((gfp_flags & GFP_MOVABLE_MASK) == GFP_MOVABLE_MASK);
>
> so I assume that mapping_gfp_mask() already had __GFP_MOVABLE set.
>
>
> So... which is it to be?
>
> <looks at the comments>
>
> #define __GFP_RECLAIMABLE ((__force gfp_t)0x80000u) /* Page is reclaimable */
> #define __GFP_MOVABLE ((__force gfp_t)0x100000u) /* Page is movable */
>
> well these pages are both reclaimable and moveable. Sigh.
>
> I'll just remove the __GFP_RECLAIMABLE from the above, see what that does.
In the last set of patches I sent to Christoph, the last patch flags pagecache
allocations as GFP_X_PAGECACHE. The grow_dev_page() annotation gets flagged
as GFP_NOFS_PAGECACHE (implemented as __GFP_MOVABLE) so the fix for this
problem is in the pipeline.
--
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
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>
prev parent reply other threads:[~2007-05-16 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 4:12 Christoph Lameter
2007-05-16 20:34 ` Andrew Morton
2007-05-16 20:42 ` Christoph Lameter
2007-05-16 21:48 ` 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=20070516214856.GA1718@skynet.ie \
--to=mel@skynet.ie \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
/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