From: Michal Hocko <mhocko@kernel.org>
To: roy.qing.li@gmail.com
Cc: cgroups@vger.kernel.org, linux-mm@kvack.org, hannes@cmpxchg.org,
vdavydov@virtuozzo.com
Subject: Re: [PATCH][RFC] mm: memcontrol: fix a unbalance uncharged count
Date: Tue, 31 May 2016 11:50:04 +0200 [thread overview]
Message-ID: <20160531094952.GI26128@dhcp22.suse.cz> (raw)
In-Reply-To: <1464687512-10695-1-git-send-email-roy.qing.li@gmail.com>
On Tue 31-05-16 17:38:32, roy.qing.li@gmail.com wrote:
> From: Li RongQing <roy.qing.li@gmail.com>
>
> I see the number of page of hpage_nr_pages(page) is charged if page is
> transparent huge or hugetlbfs pages; but when uncharge a huge page,
hugetlb pages do not get charged to the memcg. They have their own
hugetlbfscg controller.
> (1<<compound_order) page is uncharged, and maybe hpage_nr_pages(page) is
> not same as 1<<compound_order.
This should never happen. So this is not a fix. I guess it would a clean
up though.
> And remove VM_BUG_ON_PAGE(!PageTransHuge(page), page); since
> PageTransHuge(page) always is true, when this VM_BUG_ON_PAGE is called.
I guess we can drop this BUG_ON because nobody should be be seeing the
page at this stage so we cannot race with a THP split up. But I would
really have to look closer. This would be a patch on its own with the
full explanation though, IMHO.
> Signed-off-by: Li RongQing <roy.qing.li@gmail.com>
> ---
> mm/memcontrol.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 12aaadd..28c0137 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -5453,8 +5453,7 @@ static void uncharge_list(struct list_head *page_list)
> }
>
> if (PageTransHuge(page)) {
> - nr_pages <<= compound_order(page);
> - VM_BUG_ON_PAGE(!PageTransHuge(page), page);
> + nr_pages = hpage_nr_pages(page);
> nr_huge += nr_pages;
> }
>
> --
> 2.1.4
--
Michal Hocko
SUSE Labs
--
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>
prev parent reply other threads:[~2016-05-31 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 9:38 roy.qing.li
2016-05-31 9:50 ` Michal Hocko [this message]
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=20160531094952.GI26128@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=roy.qing.li@gmail.com \
--cc=vdavydov@virtuozzo.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