From: Shaohua Li <shli@fb.com>
To: Minchan Kim <minchan@kernel.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Kernel-team@fb.com, mhocko@suse.com, hughd@google.com,
hannes@cmpxchg.org, riel@redhat.com, mgorman@techsingularity.net,
akpm@linux-foundation.org
Subject: Re: [PATCH V4 4/6] mm: reclaim MADV_FREE pages
Date: Thu, 23 Feb 2017 22:14:13 -0800 [thread overview]
Message-ID: <20170224061412.GA86912@brenorobert-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20170224021218.GD9818@bbox>
On Fri, Feb 24, 2017 at 11:12:18AM +0900, Minchan Kim wrote:
> On Wed, Feb 22, 2017 at 10:50:42AM -0800, Shaohua Li wrote:
> > When memory pressure is high, we free MADV_FREE pages. If the pages are
> > not dirty in pte, the pages could be freed immediately. Otherwise we
> > can't reclaim them. We put the pages back to anonumous LRU list (by
> > setting SwapBacked flag) and the pages will be reclaimed in normal
> > swapout way.
> >
> > We use normal page reclaim policy. Since MADV_FREE pages are put into
> > inactive file list, such pages and inactive file pages are reclaimed
> > according to their age. This is expected, because we don't want to
> > reclaim too many MADV_FREE pages before used once pages.
> >
> > Based on Minchan's original patch
> >
> > Cc: Michal Hocko <mhocko@suse.com>
> > Cc: Minchan Kim <minchan@kernel.org>
> > Cc: Hugh Dickins <hughd@google.com>
> > Cc: Johannes Weiner <hannes@cmpxchg.org>
> > Cc: Rik van Riel <riel@redhat.com>
> > Cc: Mel Gorman <mgorman@techsingularity.net>
> > Cc: Andrew Morton <akpm@linux-foundation.org>
> > Signed-off-by: Shaohua Li <shli@fb.com>
> > ---
> > include/linux/rmap.h | 2 +-
> > mm/huge_memory.c | 2 ++
> > mm/madvise.c | 1 +
> > mm/rmap.c | 10 ++++++++--
> > mm/vmscan.c | 34 ++++++++++++++++++++++------------
> > 5 files changed, 34 insertions(+), 15 deletions(-)
> >
> > diff --git a/include/linux/rmap.h b/include/linux/rmap.h
> > index e2cd8f9..2bfd8c6 100644
> > --- a/include/linux/rmap.h
> > +++ b/include/linux/rmap.h
> > @@ -300,6 +300,6 @@ static inline int page_mkclean(struct page *page)
> > #define SWAP_AGAIN 1
> > #define SWAP_FAIL 2
> > #define SWAP_MLOCK 3
> > -#define SWAP_LZFREE 4
> > +#define SWAP_DIRTY 4
>
> Could you write down about SWAP_DIRTY in try_to_unmap's description?
>
> < snip >
>
> > diff --git a/mm/rmap.c b/mm/rmap.c
> > index c621088..083f32e 100644
> > --- a/mm/rmap.c
> > +++ b/mm/rmap.c
> > @@ -1424,6 +1424,12 @@ static int try_to_unmap_one(struct page *page, struct vm_area_struct *vma,
> > dec_mm_counter(mm, MM_ANONPAGES);
> > rp->lazyfreed++;
> > goto discard;
> > + } else if (!PageSwapBacked(page)) {
> > + /* dirty MADV_FREE page */
> > + set_pte_at(mm, address, pvmw.pte, pteval);
> > + ret = SWAP_DIRTY;
> > + page_vma_mapped_walk_done(&pvmw);
> > + break;
> > }
> >
> > if (swap_duplicate(entry) < 0) {
> > @@ -1525,8 +1531,8 @@ int try_to_unmap(struct page *page, enum ttu_flags flags)
> >
> > if (ret != SWAP_MLOCK && !page_mapcount(page)) {
> > ret = SWAP_SUCCESS;
> > - if (rp.lazyfreed && !PageDirty(page))
> > - ret = SWAP_LZFREE;
> > + if (rp.lazyfreed && PageDirty(page))
> > + ret = SWAP_DIRTY;
>
> Hmm, I don't understand why we need to introduce new return value.
> Can't we set SetPageSwapBacked and return SWAP_FAIL in try_to_unmap_one?
Original idea in my mind is to activate page in SWAP_DIRTY but not activate
page in SWAP_FAIL for other failures. But later we choose to ignore all corner
cases and always activate pages for all failures. So you are right, we don't
need the new return value right now.
Thanks,
Shaohua
--
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:[~2017-02-24 6:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 18:50 [PATCH V4 0/6] mm: fix some MADV_FREE issues Shaohua Li
2017-02-22 18:50 ` [PATCH V4 1/6] mm: delete unnecessary TTU_* flags Shaohua Li
2017-02-23 15:35 ` Johannes Weiner
2017-02-24 1:25 ` Minchan Kim
2017-02-24 3:29 ` Hillf Danton
2017-02-22 18:50 ` [PATCH V4 2/6] mm: don't assume anonymous pages have SwapBacked flag Shaohua Li
2017-02-22 18:50 ` [PATCH V4 3/6] mm: move MADV_FREE pages into LRU_INACTIVE_FILE list Shaohua Li
2017-02-23 15:58 ` Johannes Weiner
2017-02-23 16:26 ` Shaohua Li
2017-02-23 18:22 ` Johannes Weiner
2017-02-23 19:04 ` Shaohua Li
2017-02-24 1:49 ` Minchan Kim
2017-02-24 6:15 ` Shaohua Li
2017-02-24 23:37 ` Minchan Kim
2017-02-22 18:50 ` [PATCH V4 4/6] mm: reclaim MADV_FREE pages Shaohua Li
2017-02-23 16:13 ` Johannes Weiner
2017-02-23 17:19 ` Shaohua Li
2017-02-24 2:12 ` Minchan Kim
2017-02-24 6:14 ` Shaohua Li [this message]
2017-02-24 15:36 ` Johannes Weiner
2017-02-24 23:26 ` Minchan Kim
2017-02-22 18:50 ` [PATCH V4 5/6] mm: enable MADV_FREE for swapless system Shaohua Li
2017-02-22 18:50 ` [PATCH V4 6/6] proc: show MADV_FREE pages info in smaps Shaohua Li
2017-02-23 16:16 ` Johannes Weiner
2017-02-24 2:13 ` Minchan Kim
2017-02-24 17:08 ` Dave Hansen
2017-02-24 21:47 ` Shaohua Li
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=20170224061412.GA86912@brenorobert-mbp.dhcp.thefacebook.com \
--to=shli@fb.com \
--cc=Kernel-team@fb.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--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