From: Badari Pulavarty <pbadari@gmail.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: mel@csn.ul.ie, 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: Fri, 02 Nov 2007 08:46:42 -0800 [thread overview]
Message-ID: <1194022002.1547.19.camel@dyn9047017100.beaverton.ibm.com> (raw)
In-Reply-To: <1193940626.26106.13.camel@dyn9047017100.beaverton.ibm.com>
On Thu, 2007-11-01 at 10:10 -0800, Badari Pulavarty wrote:
> On Thu, 2007-11-01 at 11:51 -0400, Chris Mason wrote:
> > On Thu, 01 Nov 2007 08:38:57 -0800
> > Badari Pulavarty <pbadari@us.ibm.com> wrote:
> >
> > > On Wed, 2007-10-31 at 13:40 -0400, Chris Mason wrote:
> > > > On Wed, 31 Oct 2007 08:14:21 -0800
> > > > Badari Pulavarty <pbadari@us.ibm.com> wrote:
> > > > >
> > > > > I tried data=writeback mode and it didn't help :(
> > > >
> > > > Ouch, so much for the easy way out.
> > > >
> > > > >
> > > > > unable to release the page 262070
> > > > > bh c0000000211b9408 flags 110029 count 1 private 0
> > > > > unable to release the page 262098
> > > > > bh c000000020ec9198 flags 110029 count 1 private 0
> > > > > memory offlining 3f000 to 40000 failed
> > > > >
> > > >
> > > > The only other special thing reiserfs does with the page cache is
> > > > file tails. I don't suppose all of these pages are index zero in
> > > > files smaller than 4k?
> > >
> > > Ahhhhhhhhhhhhh !! I am so blind :(
> > >
> > > I have been suspecting reiserfs all along, since its executing
> > > fallback_migrate_page(). Actually, these buffer heads are
> > > backing blockdev. I guess these are metadata buffers :(
> > > I am not sure we can do much with these..
> >
> > 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 ?
>
BTW, I am having better luck with being able to offline sections
of memory on x86-64, if I take out __GFP_MOVABLE flag for
blockdev pages. (in grow_dev_page()).
Thanks,
Badari
--
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>
next prev parent reply other threads:[~2007-11-02 15:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 18:27 Badari Pulavarty
2007-10-30 17:54 ` Chris Mason
2007-10-30 21:54 ` Badari Pulavarty
2007-10-30 22:58 ` Chris Mason
2007-10-30 23:08 ` Badari
2007-10-31 0:05 ` Zan Lynx
2007-10-31 16:14 ` Badari Pulavarty
2007-10-31 17:40 ` Chris Mason
2007-11-01 16:38 ` Badari Pulavarty
2007-11-01 15:51 ` Chris Mason
2007-11-01 18:10 ` Badari Pulavarty
2007-11-02 16:46 ` Badari Pulavarty [this message]
2007-11-05 10:23 ` Mel Gorman
2007-11-05 13:40 ` Chris Mason
2007-11-05 22:46 ` Christoph Lameter
2007-11-07 14:56 ` Mel Gorman
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=1194022002.1547.19.camel@dyn9047017100.beaverton.ibm.com \
--to=pbadari@gmail.com \
--cc=chris.mason@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox