From: dong <bauers@126.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Vladimir Davydov <vdavydov.dev@gmail.com>,
Johannes Weiner <hannes@cmpxchg.org>,
bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
duanxiongchun@bytedance.com
Subject: Re:Re: Re:Re: Re: [Bug 201699] New: kmemleak in memcg_create_kmem_cache
Date: Wed, 21 Nov 2018 17:22:18 +0800 (CST) [thread overview]
Message-ID: <5fa306b3.7c7c.1673593d0d8.Coremail.bauers@126.com> (raw)
In-Reply-To: <20181121091041.GM12932@dhcp22.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 472 bytes --]
Thanks for replying, Michal.
cc to duanxiongchun
At 2018-11-21 17:10:41, "Michal Hocko" <mhocko@kernel.org> wrote:
>On Wed 21-11-18 16:46:48, dong wrote:
>> The last question: If I alloc many small pages and not free them, will
>> I exhaust the memory ( because every page contains `mem_cgroup` )?
>
>No, the memory will get reclaimed on the memory pressure or for
>anonymous one (malloc) when the process allocating it terminates,
>--
>Michal Hocko
>SUSE Labs
[-- Attachment #2: Type: text/html, Size: 857 bytes --]
next prev parent reply other threads:[~2018-11-21 9:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-201699-27@https.bugzilla.kernel.org/>
2018-11-15 21:06 ` Andrew Morton
2018-11-16 2:23 ` dong
2018-11-16 3:04 ` dong
2018-11-16 3:37 ` dong
2018-11-16 17:50 ` Vladimir Davydov
2018-11-18 0:44 ` dong
2018-11-19 8:30 ` Vladimir Davydov
2018-11-19 10:24 ` Michal Hocko
2018-11-19 11:56 ` dong
2018-11-21 8:46 ` dong
2018-11-21 8:56 ` Vladimir Davydov
2018-11-21 9:06 ` dong
2018-11-21 9:10 ` Michal Hocko
2018-11-21 9:22 ` dong [this message]
2018-11-21 9:36 ` 段熊春
2018-11-21 16:27 ` Michal Hocko
2018-11-22 2:19 ` 段熊春
2018-11-22 7:32 ` Michal Hocko
2018-11-22 2:56 ` 段熊春
2018-11-22 7:34 ` Michal Hocko
2018-11-22 8:21 ` 段熊春
2018-11-23 6:54 ` 段熊春
2018-11-21 8:52 ` Re: " Vladimir Davydov
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=5fa306b3.7c7c.1673593d0d8.Coremail.bauers@126.com \
--to=bauers@126.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=duanxiongchun@bytedance.com \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=vdavydov.dev@gmail.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