From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: Rik van Riel <riel@redhat.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: [PATCH] undo the brd.c part of ramfs-and-ram-disk-pages-are-unevictable.patch
Date: Thu, 12 Jun 2008 15:00:57 -0400 [thread overview]
Message-ID: <1213297257.6240.15.camel@lts-notebook> (raw)
In-Reply-To: <20080612135353.2d17436a@cuia.bos.redhat.com>
On Thu, 2008-06-12 at 13:53 -0400, Rik van Riel wrote:
> Undo the brd.c part of ramfs-and-ram-disk-pages-are-unevictable.patch.
> The brd pages do not live on the LRU at all, so there is no need to
> play these tricks.
Does this mean that these pages cannot be migrated? E.g., to evacuate
memory for hotplug? Looks like all paths to migrate_pages() construct a
list of pages to migrate by isolating them from the lru
[isolate_lru_page()]. Any pages not found in the lru are skipped.
Lee
>
> Debugged-by: Nick Piggin <nickpiggin@yahoo.com.au>
> Signed-off-by: Rik van Riel <riel@redhat.com>
>
> ---
> drivers/block/brd.c | 13 -------------
> 1 file changed, 13 deletions(-)
>
> Index: linux-2.6.26-rc5-mm2/drivers/block/brd.c
> ===================================================================
> --- linux-2.6.26-rc5-mm2.orig/drivers/block/brd.c 2008-06-11 14:39:43.000000000 -0400
> +++ linux-2.6.26-rc5-mm2/drivers/block/brd.c 2008-06-12 13:49:18.000000000 -0400
> @@ -374,21 +374,8 @@ static int brd_ioctl(struct inode *inode
> return error;
> }
>
> -/*
> - * brd_open():
> - * Just mark the mapping as containing unevictable pages
> - */
> -static int brd_open(struct inode *inode, struct file *filp)
> -{
> - struct address_space *mapping = inode->i_mapping;
> -
> - mapping_set_unevictable(mapping);
> - return 0;
> -}
> -
> static struct block_device_operations brd_fops = {
> .owner = THIS_MODULE,
> - .open = brd_open,
> .ioctl = brd_ioctl,
> #ifdef CONFIG_BLK_DEV_XIP
> .direct_access = brd_direct_access,
>
next prev parent reply other threads:[~2008-06-12 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 17:53 Rik van Riel
2008-06-12 19:00 ` Lee Schermerhorn [this message]
2008-06-12 19:05 ` Rik van Riel
2008-06-12 19:08 ` Nick Piggin
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=1213297257.6240.15.camel@lts-notebook \
--to=lee.schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--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
all inboxes | Powered by JetHome®