All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Mel Gorman <mel@skynet.ie>
Cc: Badari Pulavarty <pbadari@us.ibm.com>,
	reiserfs-devel@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: migratepage failures on reiserfs
Date: Mon, 5 Nov 2007 08:40:48 -0500	[thread overview]
Message-ID: <20071105084048.28035e52@think.oraclecorp.com> (raw)
In-Reply-To: <20071105102335.GA6272@skynet.ie>

On Mon, 5 Nov 2007 10:23:35 +0000
mel@skynet.ie (Mel Gorman) wrote:

> On (01/11/07 10:10), Badari Pulavarty didst pronounce:
>
> > > Hmpf, my first reply had a paragraph about the block device inode
> > > pages, I noticed the phrase file data pages and deleted it ;)
> > > 
> > > But, for the metadata buffers there's not much we can do.  They
> > > are included in a bunch of different lists and the patch would
> > > be non-trivial.
> > 
> > Unfortunately, these buffer pages are spread all around making
> > those sections of memory non-removable. Of course, one can use
> > ZONE_MOVABLE to make sure to guarantee the remove. But I am
> > hoping we could easily group all these allocations and minimize
> > spreading them around. Mel ?
> 
> The grow_dev_page() pages should be reclaimable even though migration
> is not supported for those pages? They were marked movable as it was
> useful for lumpy reclaim taking back pages for hugepage allocations
> and the like. Would it make sense for memory unremove to attempt
> migration first and reclaim second?
> 

In this case, reiserfs has the page pinned while it is doing journal
magic.  Not sure if ext3 has the same issues.

-chris

WARNING: multiple messages have this Message-ID (diff)
From: Chris Mason <chris.mason@oracle.com>
To: mel@skynet.ie (Mel Gorman)
Cc: Badari Pulavarty <pbadari@us.ibm.com>,
	reiserfs-devel@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: migratepage failures on reiserfs
Date: Mon, 5 Nov 2007 08:40:48 -0500	[thread overview]
Message-ID: <20071105084048.28035e52@think.oraclecorp.com> (raw)
In-Reply-To: <20071105102335.GA6272@skynet.ie>

On Mon, 5 Nov 2007 10:23:35 +0000
mel@skynet.ie (Mel Gorman) wrote:

> On (01/11/07 10:10), Badari Pulavarty didst pronounce:
>
> > > Hmpf, my first reply had a paragraph about the block device inode
> > > pages, I noticed the phrase file data pages and deleted it ;)
> > > 
> > > But, for the metadata buffers there's not much we can do.  They
> > > are included in a bunch of different lists and the patch would
> > > be non-trivial.
> > 
> > Unfortunately, these buffer pages are spread all around making
> > those sections of memory non-removable. Of course, one can use
> > ZONE_MOVABLE to make sure to guarantee the remove. But I am
> > hoping we could easily group all these allocations and minimize
> > spreading them around. Mel ?
> 
> The grow_dev_page() pages should be reclaimable even though migration
> is not supported for those pages? They were marked movable as it was
> useful for lumpy reclaim taking back pages for hugepage allocations
> and the like. Would it make sense for memory unremove to attempt
> migration first and reclaim second?
> 

In this case, reiserfs has the page pinned while it is doing journal
magic.  Not sure if ext3 has the same issues.

-chris

WARNING: multiple messages have this Message-ID (diff)
From: Chris Mason <chris.mason@oracle.com>
To: Mel Gorman <mel@skynet.ie>
Cc: Badari Pulavarty <pbadari@us.ibm.com>,
	reiserfs-devel@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: migratepage failures on reiserfs
Date: Mon, 5 Nov 2007 08:40:48 -0500	[thread overview]
Message-ID: <20071105084048.28035e52@think.oraclecorp.com> (raw)
In-Reply-To: <20071105102335.GA6272@skynet.ie>

On Mon, 5 Nov 2007 10:23:35 +0000
mel@skynet.ie (Mel Gorman) wrote:

> On (01/11/07 10:10), Badari Pulavarty didst pronounce:
>
> > > Hmpf, my first reply had a paragraph about the block device inode
> > > pages, I noticed the phrase file data pages and deleted it ;)
> > > 
> > > But, for the metadata buffers there's not much we can do.  They
> > > are included in a bunch of different lists and the patch would
> > > be non-trivial.
> > 
> > Unfortunately, these buffer pages are spread all around making
> > those sections of memory non-removable. Of course, one can use
> > ZONE_MOVABLE to make sure to guarantee the remove. But I am
> > hoping we could easily group all these allocations and minimize
> > spreading them around. Mel ?
> 
> The grow_dev_page() pages should be reclaimable even though migration
> is not supported for those pages? They were marked movable as it was
> useful for lumpy reclaim taking back pages for hugepage allocations
> and the like. Would it make sense for memory unremove to attempt
> migration first and reclaim second?
> 

In this case, reiserfs has the page pinned while it is doing journal
magic.  Not sure if ext3 has the same issues.

-chris

--
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:[~2007-11-05 13:40 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-30 18:27 migratepage failures on reiserfs Badari Pulavarty
2007-10-30 18:27 ` Badari Pulavarty
2007-10-30 17:54 ` Chris Mason
2007-10-30 17:54   ` Chris Mason
2007-10-30 21:54   ` Badari Pulavarty
2007-10-30 21:54     ` Badari Pulavarty
2007-10-30 22:58     ` Chris Mason
2007-10-30 22:58       ` Chris Mason
2007-10-30 23:08       ` Badari
2007-10-30 23:08         ` Badari
2007-10-31  0:05         ` Zan Lynx
2007-10-31 16:14       ` Badari Pulavarty
2007-10-31 16:14         ` Badari Pulavarty
2007-10-31 17:40         ` Chris Mason
2007-10-31 17:40           ` Chris Mason
2007-11-01 16:38           ` Badari Pulavarty
2007-11-01 16:38             ` Badari Pulavarty
2007-11-01 15:51             ` Chris Mason
2007-11-01 15:51               ` Chris Mason
2007-11-01 18:10               ` Badari Pulavarty
2007-11-01 18:10                 ` Badari Pulavarty
2007-11-02 16:46                 ` Badari Pulavarty
2007-11-02 16:46                   ` Badari Pulavarty
2007-11-05 10:23                 ` Mel Gorman
2007-11-05 10:23                   ` Mel Gorman
2007-11-05 13:40                   ` Chris Mason [this message]
2007-11-05 13:40                     ` Chris Mason
2007-11-05 13:40                     ` Chris Mason
2007-11-05 22:46                   ` Christoph Lameter
2007-11-05 22:46                     ` Christoph Lameter
2007-11-07 14:56                     ` Mel Gorman
2007-11-07 14:56                       ` Mel Gorman
2007-11-07 15:58                       ` Badari Pulavarty
2007-11-07 15:58                         ` Badari Pulavarty
2007-11-07 15:58                         ` Badari Pulavarty

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=20071105084048.28035e52@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@skynet.ie \
    --cc=pbadari@us.ibm.com \
    --cc=reiserfs-devel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.