From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Minchan Kim <minchan.kim@gmail.com>
Cc: kosaki.motohiro@jp.fujitsu.com,
Wu Fengguang <fengguang.wu@intel.com>,
Andreas Mohr <andi@lisas.de>, Jens Axboe <axboe@kernel.dk>,
Linux Memory Management List <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rik van Riel <riel@redhat.com>,
Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Subject: Re: [PATCH] vmscan: page_check_references() check low order lumpy reclaim properly
Date: Fri, 16 Apr 2010 14:33:36 +0900 (JST) [thread overview]
Message-ID: <20100416143134.27B9.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <t2j28c262361004152126t1975cd96kc21e54f3a9e41f82@mail.gmail.com>
> > + A A A /*
> > + A A A A * If we need a large contiguous chunk of memory, or have
> > + A A A A * trouble getting a small set of contiguous pages, we
> > + A A A A * will reclaim both active and inactive pages.
> > + A A A A */
> > + A A A if (sc->order > PAGE_ALLOC_COSTLY_ORDER)
> > + A A A A A A A sc->lumpy_reclaim = 1;
> > + A A A else if (sc->order && priority < DEF_PRIORITY - 2)
> > + A A A A A A A sc->lumpy_reclaim = 1;
> > + A A A else
> > + A A A A A A A sc->lumpy_reclaim = 0;
>
> How about making new function for readability instead of nesting else?
> int is_lumpy_reclaim(struct scan_control *sc)
> {
> ....
> }
>
> If you merge patch reduced stack usage of reclaim path, I think it's
> enough alone scan_control argument.
> It's just nitpick. :)
> If you don't mind, ignore, please.
Good opinion. I don't hope introduce the dependency of "reduced stack usage"
series. but I agree that I'll push your proposal later and separately.
--
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:[~2010-04-16 5:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100404221349.GA18036@rhlx01.hs-esslingen.de>
[not found] ` <20100405105319.GA16528@rhlx01.hs-esslingen.de>
2010-04-07 7:00 ` 32GB SSD on USB1.1 P3/700 == ___HELL___ (2.6.34-rc3) Wu Fengguang
2010-04-07 7:08 ` Wu Fengguang
2010-04-15 3:31 ` KOSAKI Motohiro
2010-04-15 4:19 ` Wu Fengguang
2010-04-15 4:32 ` KOSAKI Motohiro
2010-04-15 4:41 ` Wu Fengguang
2010-04-15 4:55 ` KOSAKI Motohiro
2010-04-15 5:19 ` Wu Fengguang
2010-04-16 3:16 ` [PATCH] vmscan: page_check_references() check low order lumpy reclaim properly KOSAKI Motohiro
2010-04-16 4:26 ` Minchan Kim
2010-04-16 5:33 ` KOSAKI Motohiro [this message]
2010-04-16 21:18 ` Andrew Morton
2010-05-13 2:54 ` KOSAKI Motohiro
2010-04-07 8:39 ` 32GB SSD on USB1.1 P3/700 == ___HELL___ (2.6.34-rc3) Minchan Kim
2010-04-07 8:52 ` Wu Fengguang
2010-04-07 11:17 ` Andreas Mohr
2010-04-08 19:46 ` Andreas Mohr
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=20100416143134.27B9.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=andi@lisas.de \
--cc=axboe@kernel.dk \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--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