From: Johannes Weiner <hannes@cmpxchg.org> To: Michal Hocko <mhocko@kernel.org> Cc: Vladimir Davydov <vdavydov@virtuozzo.com>, Andrew Morton <akpm@linux-foundation.org>, Tejun Heo <tj@kernel.org>, Greg Thelen <gthelen@google.com>, linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/5] memcg/kmem: switch to white list policy Date: Mon, 9 Nov 2015 11:45:18 -0500 [thread overview] Message-ID: <20151109164518.GA23356@cmpxchg.org> (raw) In-Reply-To: <20151109140832.GE8916@dhcp22.suse.cz> On Mon, Nov 09, 2015 at 03:08:32PM +0100, Michal Hocko wrote: > I am _all_ for this semantic I am just not sure what to do with the > legacy kmem controller. Can we change its semantic? If we cannot do that > we would have to distinguish legacy and unified hierarchies during > runtime and add the flag automagically for the first one (that would > however require to keep __GFP_NOACCOUNT as well) which is all as clear > as mud. But maybe the workloads which are using kmem legacy API can cope > with that. I think we can make that change for the existing kmem accounting too, simply because the whitelist should be covering all memory consumers that actually matter for isolation in practice. Yes, there is a risk for accidents, but we are not actually intending to change semantics. > Anyway if we go this way then I think the kmem accounting would be safe > to be enabled by default with the cgroup2. Cool, I'm happy we're on the same page about this.
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Weiner <hannes@cmpxchg.org> To: Michal Hocko <mhocko@kernel.org> Cc: Vladimir Davydov <vdavydov@virtuozzo.com>, Andrew Morton <akpm@linux-foundation.org>, Tejun Heo <tj@kernel.org>, Greg Thelen <gthelen@google.com>, linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/5] memcg/kmem: switch to white list policy Date: Mon, 9 Nov 2015 11:45:18 -0500 [thread overview] Message-ID: <20151109164518.GA23356@cmpxchg.org> (raw) In-Reply-To: <20151109140832.GE8916@dhcp22.suse.cz> On Mon, Nov 09, 2015 at 03:08:32PM +0100, Michal Hocko wrote: > I am _all_ for this semantic I am just not sure what to do with the > legacy kmem controller. Can we change its semantic? If we cannot do that > we would have to distinguish legacy and unified hierarchies during > runtime and add the flag automagically for the first one (that would > however require to keep __GFP_NOACCOUNT as well) which is all as clear > as mud. But maybe the workloads which are using kmem legacy API can cope > with that. I think we can make that change for the existing kmem accounting too, simply because the whitelist should be covering all memory consumers that actually matter for isolation in practice. Yes, there is a risk for accidents, but we are not actually intending to change semantics. > Anyway if we go this way then I think the kmem accounting would be safe > to be enabled by default with the cgroup2. Cool, I'm happy we're on the same page about this. -- 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:[~2015-11-09 16:45 UTC|newest] Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-11-07 20:07 [PATCH 0/5] memcg/kmem: switch to white list policy Vladimir Davydov 2015-11-07 20:07 ` Vladimir Davydov 2015-11-07 20:07 ` Vladimir Davydov 2015-11-07 20:07 ` [PATCH 1/5] Revert "kernfs: do not account ino_ida allocations to memcg" Vladimir Davydov 2015-11-07 20:07 ` Vladimir Davydov 2015-11-07 20:07 ` Vladimir Davydov 2015-11-07 20:07 ` [PATCH 2/5] Revert "gfp: add __GFP_NOACCOUNT" Vladimir Davydov 2015-11-07 20:07 ` Vladimir Davydov 2015-11-07 20:07 ` [PATCH 3/5] memcg: only account kmem allocations marked as __GFP_ACCOUNT Vladimir Davydov 2015-11-07 20:07 ` Vladimir Davydov 2015-11-07 20:07 ` [PATCH 4/5] vmalloc: allow to account vmalloc to memcg Vladimir Davydov 2015-11-07 20:07 ` Vladimir Davydov 2015-11-07 20:07 ` [PATCH 5/5] Account certain kmem allocations " Vladimir Davydov 2015-11-07 20:07 ` Vladimir Davydov 2015-11-09 14:39 ` Michal Hocko 2015-11-09 14:39 ` Michal Hocko 2015-11-10 8:07 ` Vladimir Davydov 2015-11-10 8:07 ` Vladimir Davydov 2015-11-10 8:07 ` Vladimir Davydov 2015-11-10 13:23 ` Michal Hocko 2015-11-10 13:23 ` Michal Hocko 2015-11-10 13:23 ` Michal Hocko 2015-11-09 14:08 ` [PATCH 0/5] memcg/kmem: switch to white list policy Michal Hocko 2015-11-09 14:08 ` Michal Hocko 2015-11-09 16:45 ` Johannes Weiner [this message] 2015-11-09 16:45 ` Johannes Weiner 2015-11-09 18:28 ` Vladimir Davydov 2015-11-09 18:28 ` Vladimir Davydov 2015-11-09 18:28 ` Vladimir Davydov 2015-11-09 18:54 ` Tejun Heo 2015-11-09 18:54 ` Tejun Heo 2015-11-09 19:27 ` Vladimir Davydov 2015-11-09 19:27 ` Vladimir Davydov 2015-11-09 19:27 ` Vladimir Davydov 2015-11-09 19:32 ` Tejun Heo 2015-11-09 19:32 ` Tejun Heo 2015-11-09 20:12 ` Vladimir Davydov 2015-11-09 20:12 ` Vladimir Davydov 2015-11-09 20:12 ` Vladimir Davydov 2015-11-09 20:30 ` Tejun Heo 2015-11-09 20:30 ` Tejun Heo 2015-11-09 20:30 ` Tejun Heo 2015-11-10 7:49 ` Vladimir Davydov 2015-11-10 7:49 ` Vladimir Davydov 2015-11-11 8:12 ` Michal Hocko 2015-11-11 8:12 ` Michal Hocko 2015-11-11 8:12 ` 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=20151109164518.GA23356@cmpxchg.org \ --to=hannes@cmpxchg.org \ --cc=akpm@linux-foundation.org \ --cc=cgroups@vger.kernel.org \ --cc=gthelen@google.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mhocko@kernel.org \ --cc=tj@kernel.org \ --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: linkBe 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.