linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org
Subject: grow_dev_page's __GFP_MOVABLE
Date: Tue, 11 Mar 2008 21:33:18 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0803112116380.18085@blonde.site> (raw)

Hi Mel,

I'm (slightly) worried by your __GFP_MOVABLE in grow_dev_page:
is it valid, given that we come here for filesystem metadata pages
- don't we?  If it is valid, then wouldn't adding __GFP_HIGHMEM
be valid there also?  It'd be very nice to have __GFP_MOVABLE and
__GFP_HIGHMEM on all blockdev pages, but we've concluded in the
past that __GFP_HIGHMEM cannot be allowed without large kmapping
mods throughout the filesystems.  Go back to GFP_NOFS there?

Hugh

--- 2.6.25-rc5/fs/buffer.c	2008-03-05 10:47:40.000000000 +0000
+++ linux/fs/buffer.c	2008-03-11 21:21:10.000000000 +0000
@@ -1029,8 +1029,7 @@ grow_dev_page(struct block_device *bdev,
 	struct page *page;
 	struct buffer_head *bh;
 
-	page = find_or_create_page(inode->i_mapping, index,
-		(mapping_gfp_mask(inode->i_mapping) & ~__GFP_FS)|__GFP_MOVABLE);
+	page = find_or_create_page(inode->i_mapping, index, GFP_NOFS);
 	if (!page)
 		return NULL;
 

--
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>

             reply	other threads:[~2008-03-11 21:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 21:33 Hugh Dickins [this message]
2008-03-12 14:08 ` Mel Gorman
2008-03-12 18:11   ` Hugh Dickins
2008-03-13 12:07     ` Mel Gorman
2008-03-13 15:05       ` Badari Pulavarty
2008-03-13 15:44         ` Mel Gorman
2008-03-14  0:50           ` Badari Pulavarty
2008-03-14 11:47             ` Mel Gorman
2008-03-14 16:05               ` Badari Pulavarty
2008-03-14 18:52                 ` Badari Pulavarty
2008-03-17 10:54                   ` Andy Whitcroft
2008-03-17 14:04                     ` Badari Pulavarty
2008-03-18  9:34                 ` Mel Gorman

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=Pine.LNX.4.64.0803112116380.18085@blonde.site \
    --to=hugh@veritas.com \
    --cc=akpm@linux-foundation.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