From: Minchan Kim <minchan@kernel.org>
To: Chen Yucong <slaoub@gmail.com>
Cc: mgorman@suse.de, mhocko@suse.cz, hannes@cmpxchg.org,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/vmscan.c: avoid recording the original scan targets in shrink_lruvec()
Date: Tue, 10 Jun 2014 09:24:10 +0900 [thread overview]
Message-ID: <20140610002410.GB8171@bbox> (raw)
In-Reply-To: <1402359051.22759.7.camel@debian>
On Tue, Jun 10, 2014 at 08:10:51AM +0800, Chen Yucong wrote:
> On Tue, 2014-06-10 at 08:24 +0900, Minchan Kim wrote:
> > Hello,
> >
> > On Mon, Jun 09, 2014 at 09:27:16PM +0800, Chen Yucong wrote:
> > > Via https://lkml.org/lkml/2013/4/10/334 , we can find that recording the
> > > original scan targets introduces extra 40 bytes on the stack. This patch
> > > is able to avoid this situation and the call to memcpy(). At the same time,
> > > it does not change the relative design idea.
> > >
> > > ratio = original_nr_file / original_nr_anon;
> > >
> > > If (nr_file > nr_anon), then ratio = (nr_file - x) / nr_anon.
> > > x = nr_file - ratio * nr_anon;
> > >
> > > if (nr_file <= nr_anon), then ratio = nr_file / (nr_anon - x).
> > > x = nr_anon - nr_file / ratio;
> >
> > Nice cleanup!
> >
> > Below one nitpick.
> >
>
> >
> > If both nr_file and nr_anon are zero, then the nr_anon could be zero
> > if HugePage are reclaimed so that it could pass the below check
> >
> > if (nr_reclaimed < nr_to_reclaim || scan_adjusted)
> >
> >
> The Mel Gorman's patch has already handled this situation you're
> describing. It's called:
>
> mm: vmscan: use proportional scanning during direct reclaim and full
> scan at DEF_PRIORITY
It seems I was far away from vmscan.c for a while.
Thanks for the pointing out. So,
Acked-by: Minchan Kim <minchan@kernel.org>
--
Kind regards,
Minchan Kim
--
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:[~2014-06-10 0:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 13:27 [PATCH] mm/vmscan.c: avoid recording the original scan targets in shrink_lruvec() Chen Yucong
2014-06-09 23:24 ` Minchan Kim
2014-06-10 0:10 ` Chen Yucong
2014-06-10 0:24 ` Minchan Kim [this message]
2014-06-10 23:33 ` Andrew Morton
2014-06-11 2:08 ` Chen Yucong
2014-06-11 3:21 ` Chen Yucong
2014-06-16 0:47 ` Hugh Dickins
2014-06-16 6:21 ` Chen Yucong
2014-06-16 12:57 ` Chen Yucong
2014-06-16 23:42 ` Andrew Morton
2014-06-16 23:50 ` Chen Yucong
2014-06-16 23:51 ` Minchan Kim
2014-06-16 23:46 ` Minchan Kim
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=20140610002410.GB8171@bbox \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=slaoub@gmail.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;
as well as URLs for NNTP newsgroup(s).