From: Minchan Kim <minchan@kernel.org>
To: "Wang, Yalin" <Yalin.Wang@sonymobile.com>
Cc: Michal Hocko <mhocko@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Rik van Riel <riel@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Mel Gorman <mgorman@suse.de>, Shaohua Li <shli@kernel.org>
Subject: Re: [RFC] mm: change mm_advise_free to clear page dirty
Date: Fri, 27 Feb 2015 15:44:25 +0900 [thread overview]
Message-ID: <20150227064425.GB20805@blaptop> (raw)
In-Reply-To: <35FD53F367049845BC99AC72306C23D10458D6173BDE@CNBJMBX05.corpusers.net>
On Fri, Feb 27, 2015 at 01:48:48PM +0800, Wang, Yalin wrote:
> > -----Original Message-----
> > From: Minchan Kim [mailto:minchan.kim@gmail.com] On Behalf Of Minchan Kim
> > Sent: Friday, February 27, 2015 1:28 PM
> > To: Wang, Yalin
> > Cc: Michal Hocko; Andrew Morton; linux-kernel@vger.kernel.org; linux-
> > mm@kvack.org; Rik van Riel; Johannes Weiner; Mel Gorman; Shaohua Li
> > Subject: Re: [RFC] mm: change mm_advise_free to clear page dirty
> >
> > Hello,
> >
> > On Fri, Feb 27, 2015 at 11:37:18AM +0800, Wang, Yalin wrote:
> > > This patch add ClearPageDirty() to clear AnonPage dirty flag,
> > > the Anonpage mapcount must be 1, so that this page is only used by
> > > the current process, not shared by other process like fork().
> > > if not clear page dirty for this anon page, the page will never be
> > > treated as freeable.
> >
> > In case of anonymous page, it has PG_dirty when VM adds it to
> > swap cache and clear it in clear_page_dirty_for_io. That's why
> > I added ClearPageDirty if we found it in swapcache.
> > What case am I missing? It would be better to understand if you
> > describe specific scenario.
> >
> > Thanks.
> >
> > >
> > > Signed-off-by: Yalin Wang <yalin.wang@sonymobile.com>
> > > ---
> > > mm/madvise.c | 15 +++++----------
> > > 1 file changed, 5 insertions(+), 10 deletions(-)
> > >
> > > diff --git a/mm/madvise.c b/mm/madvise.c
> > > index 6d0fcb8..257925a 100644
> > > --- a/mm/madvise.c
> > > +++ b/mm/madvise.c
> > > @@ -297,22 +297,17 @@ static int madvise_free_pte_range(pmd_t *pmd,
> > unsigned long addr,
> > > continue;
> > >
> > > page = vm_normal_page(vma, addr, ptent);
> > > - if (!page)
> > > + if (!page || !PageAnon(page) || !trylock_page(page))
> > > continue;
> > >
> > > if (PageSwapCache(page)) {
> > > - if (!trylock_page(page))
> > > + if (!try_to_free_swap(page))
> > > continue;
> > > -
> > > - if (!try_to_free_swap(page)) {
> > > - unlock_page(page);
> > > - continue;
> > > - }
> > > -
> > > - ClearPageDirty(page);
> > > - unlock_page(page);
> > > }
> > >
> > > + if (page_mapcount(page) == 1)
> > > + ClearPageDirty(page);
> > > + unlock_page(page);
> > > /*
> > > * Some of architecture(ex, PPC) don't update TLB
> > > * with set_pte_at and tlb_remove_tlb_entry so for
> > > --
> Yes, for page which is in SwapCache, it is correct,
> But for anon page which is not in SwapCache, it is always
> PageDirty(), so we should also clear dirty bit to make it freeable,
No. Every anon page starts from !PageDirty and it has PG_dirty
only when it's addeded into swap cache. If vm_swap_full turns on,
a page in swap cache could have PG_dirty via try_to_free_swap again.
So, Do you have concern about swapped-out pages when MADV_FREE is
called? If so, please look at my patch.
https://lkml.org/lkml/2015/2/25/43
It will zap the swapped out page. So, this is not a issue any more?
>
> Another problem is that if an anon page is shared by more than one process,
> This happened when fork(), the anon page will be copy on write,
> In this case, we should not clear page dirty,
> This is not correct for other process which don't call MADV_FREE syscall.
You mean we shouldn't inherit MADV_FREE attribute?
Why?
parent:
ptr1 = malloc(len);
-> allocator calls mmap(len);
memset(ptr1, 'a', len);
free(ptr1);
-> allocator calss madvise_free(ptr1, len);
..
..
-> VM discard hinted pages
fork();
child:
ptr2 = malloc(len)
-> allocator reuses the chunk allocated from parent.
so, child will see zero pages from ptr2 but he doesn't write
anything so garbage|zero page anything is okay to him.
>
> Thanks
>
>
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Minchan Kim <minchan@kernel.org>
To: "Wang, Yalin" <Yalin.Wang@sonymobile.com>
Cc: Michal Hocko <mhocko@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Rik van Riel <riel@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Mel Gorman <mgorman@suse.de>, Shaohua Li <shli@kernel.org>
Subject: Re: [RFC] mm: change mm_advise_free to clear page dirty
Date: Fri, 27 Feb 2015 15:44:25 +0900 [thread overview]
Message-ID: <20150227064425.GB20805@blaptop> (raw)
In-Reply-To: <35FD53F367049845BC99AC72306C23D10458D6173BDE@CNBJMBX05.corpusers.net>
On Fri, Feb 27, 2015 at 01:48:48PM +0800, Wang, Yalin wrote:
> > -----Original Message-----
> > From: Minchan Kim [mailto:minchan.kim@gmail.com] On Behalf Of Minchan Kim
> > Sent: Friday, February 27, 2015 1:28 PM
> > To: Wang, Yalin
> > Cc: Michal Hocko; Andrew Morton; linux-kernel@vger.kernel.org; linux-
> > mm@kvack.org; Rik van Riel; Johannes Weiner; Mel Gorman; Shaohua Li
> > Subject: Re: [RFC] mm: change mm_advise_free to clear page dirty
> >
> > Hello,
> >
> > On Fri, Feb 27, 2015 at 11:37:18AM +0800, Wang, Yalin wrote:
> > > This patch add ClearPageDirty() to clear AnonPage dirty flag,
> > > the Anonpage mapcount must be 1, so that this page is only used by
> > > the current process, not shared by other process like fork().
> > > if not clear page dirty for this anon page, the page will never be
> > > treated as freeable.
> >
> > In case of anonymous page, it has PG_dirty when VM adds it to
> > swap cache and clear it in clear_page_dirty_for_io. That's why
> > I added ClearPageDirty if we found it in swapcache.
> > What case am I missing? It would be better to understand if you
> > describe specific scenario.
> >
> > Thanks.
> >
> > >
> > > Signed-off-by: Yalin Wang <yalin.wang@sonymobile.com>
> > > ---
> > > mm/madvise.c | 15 +++++----------
> > > 1 file changed, 5 insertions(+), 10 deletions(-)
> > >
> > > diff --git a/mm/madvise.c b/mm/madvise.c
> > > index 6d0fcb8..257925a 100644
> > > --- a/mm/madvise.c
> > > +++ b/mm/madvise.c
> > > @@ -297,22 +297,17 @@ static int madvise_free_pte_range(pmd_t *pmd,
> > unsigned long addr,
> > > continue;
> > >
> > > page = vm_normal_page(vma, addr, ptent);
> > > - if (!page)
> > > + if (!page || !PageAnon(page) || !trylock_page(page))
> > > continue;
> > >
> > > if (PageSwapCache(page)) {
> > > - if (!trylock_page(page))
> > > + if (!try_to_free_swap(page))
> > > continue;
> > > -
> > > - if (!try_to_free_swap(page)) {
> > > - unlock_page(page);
> > > - continue;
> > > - }
> > > -
> > > - ClearPageDirty(page);
> > > - unlock_page(page);
> > > }
> > >
> > > + if (page_mapcount(page) == 1)
> > > + ClearPageDirty(page);
> > > + unlock_page(page);
> > > /*
> > > * Some of architecture(ex, PPC) don't update TLB
> > > * with set_pte_at and tlb_remove_tlb_entry so for
> > > --
> Yes, for page which is in SwapCache, it is correct,
> But for anon page which is not in SwapCache, it is always
> PageDirty(), so we should also clear dirty bit to make it freeable,
No. Every anon page starts from !PageDirty and it has PG_dirty
only when it's addeded into swap cache. If vm_swap_full turns on,
a page in swap cache could have PG_dirty via try_to_free_swap again.
So, Do you have concern about swapped-out pages when MADV_FREE is
called? If so, please look at my patch.
https://lkml.org/lkml/2015/2/25/43
It will zap the swapped out page. So, this is not a issue any more?
>
> Another problem is that if an anon page is shared by more than one process,
> This happened when fork(), the anon page will be copy on write,
> In this case, we should not clear page dirty,
> This is not correct for other process which don't call MADV_FREE syscall.
You mean we shouldn't inherit MADV_FREE attribute?
Why?
parent:
ptr1 = malloc(len);
-> allocator calls mmap(len);
memset(ptr1, 'a', len);
free(ptr1);
-> allocator calss madvise_free(ptr1, len);
..
..
-> VM discard hinted pages
fork();
child:
ptr2 = malloc(len)
-> allocator reuses the chunk allocated from parent.
so, child will see zero pages from ptr2 but he doesn't write
anything so garbage|zero page anything is okay to him.
>
> Thanks
>
>
--
Kind regards,
Minchan Kim
next prev parent reply other threads:[~2015-02-27 6:44 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 8:18 [PATCH RFC 1/4] mm: throttle MADV_FREE Minchan Kim
2015-02-24 8:18 ` Minchan Kim
2015-02-24 8:18 ` [PATCH RFC 2/4] mm: change deactivate_page with deactivate_file_page Minchan Kim
2015-02-24 8:18 ` Minchan Kim
2015-02-24 8:18 ` [PATCH RFC 3/4] mm: move lazy free pages to inactive list Minchan Kim
2015-02-24 8:18 ` Minchan Kim
2015-02-24 16:14 ` Michal Hocko
2015-02-24 16:14 ` Michal Hocko
2015-02-25 0:27 ` Minchan Kim
2015-02-25 0:27 ` Minchan Kim
2015-02-25 15:17 ` Michal Hocko
2015-02-25 15:17 ` Michal Hocko
2015-02-24 8:18 ` [PATCH RFC 4/4] mm: support MADV_FREE in swapless system Minchan Kim
2015-02-24 8:18 ` Minchan Kim
2015-02-24 16:51 ` Michal Hocko
2015-02-24 16:51 ` Michal Hocko
2015-02-25 1:41 ` Minchan Kim
2015-02-25 1:41 ` Minchan Kim
2015-02-24 15:43 ` [PATCH RFC 1/4] mm: throttle MADV_FREE Michal Hocko
2015-02-24 15:43 ` Michal Hocko
2015-02-24 22:54 ` Shaohua Li
2015-02-24 22:54 ` Shaohua Li
2015-02-25 14:13 ` Michal Hocko
2015-02-25 14:13 ` Michal Hocko
2015-02-25 0:08 ` Minchan Kim
2015-02-25 0:08 ` Minchan Kim
2015-02-25 7:11 ` Minchan Kim
2015-02-25 7:11 ` Minchan Kim
2015-02-25 15:07 ` Michal Hocko
2015-02-25 15:07 ` Michal Hocko
2015-02-25 18:37 ` Shaohua Li
2015-02-25 18:37 ` Shaohua Li
2015-02-26 0:42 ` Minchan Kim
2015-02-26 0:42 ` Minchan Kim
2015-02-26 19:04 ` Shaohua Li
2015-02-26 19:04 ` Shaohua Li
2015-02-27 3:37 ` [RFC] mm: change mm_advise_free to clear page dirty Wang, Yalin
2015-02-27 3:37 ` Wang, Yalin
2015-02-27 5:28 ` Minchan Kim
2015-02-27 5:28 ` Minchan Kim
2015-02-27 5:48 ` Wang, Yalin
2015-02-27 5:48 ` Wang, Yalin
2015-02-27 6:44 ` Minchan Kim [this message]
2015-02-27 6:44 ` Minchan Kim
2015-02-27 7:50 ` Wang, Yalin
2015-02-27 7:50 ` Wang, Yalin
2015-02-27 13:37 ` Minchan Kim
2015-02-27 13:37 ` Minchan Kim
2015-02-28 13:50 ` Minchan Kim
2015-02-28 13:50 ` Minchan Kim
2015-03-02 1:59 ` Wang, Yalin
2015-03-02 1:59 ` Wang, Yalin
2015-03-03 0:42 ` Minchan Kim
2015-03-03 0:42 ` Minchan Kim
2015-02-28 13:50 ` [RFC] mm: change mm_advise_free to clear page dirty, " Minchan Kim
2015-02-27 21:02 ` Michal Hocko
2015-02-27 21:02 ` Michal Hocko
2015-02-28 2:11 ` Wang, Yalin
2015-02-28 2:11 ` Wang, Yalin
2015-02-28 6:01 ` [RFC V2] " Wang, Yalin
2015-02-28 6:01 ` Wang, Yalin
2015-03-02 12:38 ` Michal Hocko
2015-03-02 12:38 ` Michal Hocko
2015-03-03 2:06 ` [RFC V3] " Wang, Yalin
2015-03-03 2:06 ` Wang, Yalin
2015-02-28 13:55 ` [RFC] " Minchan Kim
2015-02-28 13:55 ` Minchan Kim
2015-03-02 1:53 ` Wang, Yalin
2015-03-02 1:53 ` Wang, Yalin
2015-03-02 12:33 ` Michal Hocko
2015-03-02 12:33 ` Michal Hocko
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=20150227064425.GB20805@blaptop \
--to=minchan@kernel.org \
--cc=Yalin.Wang@sonymobile.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 \
--cc=riel@redhat.com \
--cc=shli@kernel.org \
/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.