From: Chen Yucong <slaoub@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mgorman@suse.de, mhocko@suse.cz, hannes@cmpxchg.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: Wed, 11 Jun 2014 10:08:41 +0800 [thread overview]
Message-ID: <1402452521.28433.26.camel@debian> (raw)
In-Reply-To: <20140610163338.5b463c5884c4c7e3f1b948e2@linux-foundation.org>
On Tue, 2014-06-10 at 16:33 -0700, Andrew Morton wrote:
> On Mon, 9 Jun 2014 21:27:16 +0800 Chen Yucong <slaoub@gmail.com> 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;
> >
> > ...
> >
>
> Are you sure this is an equivalent-to-before change? If so, then I
> can't immediately see why :(
>
The relative design idea is to keep
ratio
== scan_target[anon] : scan_target[file]
== really_scanned_num[anon] : really_scanned_num[file]
The original implementation is
ratio
== (scan_target[anon] * percentage_anon) /
(scan_target[file] * percentage_file)
To keep the original ratio, percentage_anon should equal to
percentage_file. In other word, we need to calculate the difference
value between percentage_anon and percentage_file, we also have to
record the original scan targets for this.
Instead, we can calculate the *ratio* at the beginning of
shrink_lruvec(). As a result, this can avoid introducing the extra 40
bytes.
In short, we have the same goal: keep the same *ratio* from beginning to
end.
thx!
cyc
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Chen Yucong <slaoub@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mgorman@suse.de, mhocko@suse.cz, hannes@cmpxchg.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: Wed, 11 Jun 2014 10:08:41 +0800 [thread overview]
Message-ID: <1402452521.28433.26.camel@debian> (raw)
In-Reply-To: <20140610163338.5b463c5884c4c7e3f1b948e2@linux-foundation.org>
On Tue, 2014-06-10 at 16:33 -0700, Andrew Morton wrote:
> On Mon, 9 Jun 2014 21:27:16 +0800 Chen Yucong <slaoub@gmail.com> 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;
> >
> > ...
> >
>
> Are you sure this is an equivalent-to-before change? If so, then I
> can't immediately see why :(
>
The relative design idea is to keep
ratio
== scan_target[anon] : scan_target[file]
== really_scanned_num[anon] : really_scanned_num[file]
The original implementation is
ratio
== (scan_target[anon] * percentage_anon) /
(scan_target[file] * percentage_file)
To keep the original ratio, percentage_anon should equal to
percentage_file. In other word, we need to calculate the difference
value between percentage_anon and percentage_file, we also have to
record the original scan targets for this.
Instead, we can calculate the *ratio* at the beginning of
shrink_lruvec(). As a result, this can avoid introducing the extra 40
bytes.
In short, we have the same goal: keep the same *ratio* from beginning to
end.
thx!
cyc
next prev parent reply other threads:[~2014-06-11 2:10 UTC|newest]
Thread overview: 28+ 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 13:27 ` Chen Yucong
2014-06-09 23:24 ` Minchan Kim
2014-06-09 23:24 ` Minchan Kim
2014-06-10 0:10 ` Chen Yucong
2014-06-10 0:10 ` Chen Yucong
2014-06-10 0:24 ` Minchan Kim
2014-06-10 0:24 ` Minchan Kim
2014-06-10 23:33 ` Andrew Morton
2014-06-10 23:33 ` Andrew Morton
2014-06-11 2:08 ` Chen Yucong [this message]
2014-06-11 2:08 ` Chen Yucong
2014-06-11 3:21 ` Chen Yucong
2014-06-11 3:21 ` Chen Yucong
2014-06-16 0:47 ` Hugh Dickins
2014-06-16 0:47 ` Hugh Dickins
2014-06-16 6:21 ` Chen Yucong
2014-06-16 6:21 ` Chen Yucong
2014-06-16 12:57 ` Chen Yucong
2014-06-16 12:57 ` Chen Yucong
2014-06-16 23:42 ` Andrew Morton
2014-06-16 23:42 ` Andrew Morton
2014-06-16 23:50 ` Chen Yucong
2014-06-16 23:50 ` Chen Yucong
2014-06-16 23:51 ` Minchan Kim
2014-06-16 23:51 ` Minchan Kim
2014-06-16 23:46 ` 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=1402452521.28433.26.camel@debian \
--to=slaoub@gmail.com \
--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 \
/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.