From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: "Wang, Yalin" <Yalin.Wang@sonymobile.com>,
"'mhocko@suse.cz'" <mhocko@suse.cz>,
"'linux-mm@kvack.org'" <linux-mm@kvack.org>,
"'akpm@linux-foundation.org'" <akpm@linux-foundation.org>,
"mm-commits@vger.kernel.org" <mm-commits@vger.kernel.org>,
"hughd@google.com" <hughd@google.com>,
"b.zolnierkie@samsung.com" <b.zolnierkie@samsung.com>
Subject: Re: [RFC] Free the reserved memblock when free cma pages
Date: Mon, 15 Sep 2014 12:06:54 +0900 [thread overview]
Message-ID: <20140915030653.GE2676@js1304-P5Q-DELUXE> (raw)
In-Reply-To: <5412BE75.8030600@samsung.com>
On Fri, Sep 12, 2014 at 11:35:49AM +0200, Marek Szyprowski wrote:
> Hello,
>
> On 2014-09-09 08:13, Wang, Yalin wrote:
> >This patch add memblock_free to also free the reserved memblock,
> >so that the cma pages are not marked as reserved memory in
> >/sys/kernel/debug/memblock/reserved debug file
> >
> >Signed-off-by: Yalin Wang <yalin.wang@sonymobile.com>
>
> Acked-by: Marek Szyprowski <m.szyprowski@samsung.com>
>
> >---
> > mm/cma.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> >diff --git a/mm/cma.c b/mm/cma.c
> >index c17751c..f3ec756 100644
> >--- a/mm/cma.c
> >+++ b/mm/cma.c
> >@@ -114,6 +114,8 @@ static int __init cma_activate_area(struct cma *cma)
> > goto err;
> > }
> > init_cma_reserved_pageblock(pfn_to_page(base_pfn));
> >+ memblock_free(__pfn_to_phys(base_pfn),
> >+ pageblock_nr_pages * PAGE_SIZE);
> > } while (--i);
> > mutex_init(&cma->lock);
>
> Right. Thanks for fixing this issue. When cma_activate_area() is
> called noone
> should use memblock to allocate memory, but it is ok to call memblock_free()
> to update memblock statistics, so users won't be confused by cma entries in
> /sys/kernel/debug/memblock/reserved file.
Maybe some comment on code would be very helpful.
Thanks.
--
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-09-15 3:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 6:13 Wang, Yalin
2014-09-10 8:18 ` Michal Hocko
2014-09-10 9:02 ` Wang, Yalin
2014-09-12 9:35 ` Marek Szyprowski
2014-09-15 3:06 ` Joonsoo Kim [this message]
2014-09-15 5:21 ` Minchan Kim
2014-09-15 5:36 ` Wang, Yalin
2014-09-15 5:42 ` Minchan Kim
2014-09-15 5:46 ` Wang, Yalin
2014-09-15 6:10 ` [RFC V2] " Wang, Yalin
2014-09-15 6:57 ` Minchan Kim
2014-09-15 7:54 ` [PATCH Resend] " Wang, Yalin
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=20140915030653.GE2676@js1304-P5Q-DELUXE \
--to=iamjoonsoo.kim@lge.com \
--cc=Yalin.Wang@sonymobile.com \
--cc=akpm@linux-foundation.org \
--cc=b.zolnierkie@samsung.com \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox