From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: jschopp@austin.ibm.com,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Linux Hotplug Memory Support <lhms-devel@lists.sourceforge.net>
Subject: Re: [Lhms-devel] Re: [Patch] New zone ZONE_EASY_RECLAIM take 4. (disable gfp_easy_reclaim bit)[5/8]
Date: Fri, 06 Jan 2006 10:36:36 +0900 [thread overview]
Message-ID: <20060106103140.5643.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <20060105112305.GB14735@skynet.ie>
> On (05/01/06 19:59), Yasunori Goto didst pronounce:
> > > On (05/01/06 14:43), Yasunori Goto didst pronounce:
> > > > >
> > > > > > ===================================================================
> > > > > > --- zone_reclaim.orig/fs/pipe.c 2005-12-16 18:36:20.000000000 +0900
> > > > > > +++ zone_reclaim/fs/pipe.c 2005-12-16 19:15:35.000000000 +0900
> > > > > > @@ -284,7 +284,7 @@ pipe_writev(struct file *filp, const str
> > > > > > int error;
> > > > > >
> > > > > > if (!page) {
> > > > > > - page = alloc_page(GFP_HIGHUSER);
> > > > > > + page = alloc_page(GFP_HIGHUSER & ~__GFP_EASY_RECLAIM);
> > > > > > if (unlikely(!page)) {
> > > > > > ret = ret ? : -ENOMEM;
> > > > > > break;
> > > > >
> > > > > That is a bit hard to understand. How about a new GFP_HIGHUSER_HARD or
> > > > > somesuch define back in patch 1, then use it here?
> > > >
> > > > It looks better. Thanks for your idea.
> > > >
> > >
> > > There are other places where GFP_HIGHUSER is used for pages that are not easily
> > > reclaimed. It is easier clearer to add __GFP_EASY_RECLAIM at the places you
> > > know pages are easily reclaimed rather than removing __GFP_EASY_RECLAIM from
> > > awkward places.
> >
> > I thought that other pages can be migrated by Chlistoph-san's (and
> > Kame-san's) patch.
>
> Then the pages are not "easily reclaimed", they can just be moved by
> some other mechanism.
Ah. My naming was no good. :-(
> > May I ask which page should be no EASY_RECLAIM?
>
> Based on http://lxr.linux.no/ident?i=GFP_HIGHUSER, examples include HugeTLB
> pages, pages allocated by the infiniband driver, pages allocated by the NFS
> driver and inode pages.
Hmmmm.
Ok. Your proposal looks better.
Thanks.
--
Yasunori Goto
--
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:[~2006-01-06 1:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 8:53 Yasunori Goto
2006-01-03 21:34 ` Joel Schopp
2006-01-05 5:43 ` Yasunori Goto
2006-01-05 9:47 ` Mel Gorman
2006-01-05 10:59 ` Yasunori Goto
2006-01-05 11:23 ` Mel Gorman
2006-01-06 1:36 ` Yasunori Goto [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=20060106103140.5643.Y-GOTO@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--cc=jschopp@austin.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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