From: Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
To: Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>
Cc: Vladimir Davydov
<vdavydov-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Christoph Lameter <cl-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org>,
Pekka Enberg <penberg-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
David Rientjes <rientjes-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
Joonsoo Kim <iamjoonsoo.kim-Hm3cg6mZ9cc@public.gmane.org>,
Greg Thelen <gthelen-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/2] gfp: add __GFP_NOACCOUNT
Date: Wed, 6 May 2015 09:16:22 -0400 [thread overview]
Message-ID: <20150506131622.GA4629@cmpxchg.org> (raw)
In-Reply-To: <20150506115941.GH14550-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
On Wed, May 06, 2015 at 01:59:41PM +0200, Michal Hocko wrote:
> On Tue 05-05-15 12:45:42, Vladimir Davydov wrote:
> > Not all kmem allocations should be accounted to memcg. The following
> > patch gives an example when accounting of a certain type of allocations
> > to memcg can effectively result in a memory leak.
>
> > This patch adds the __GFP_NOACCOUNT flag which if passed to kmalloc
> > and friends will force the allocation to go through the root
> > cgroup. It will be used by the next patch.
>
> The name of the flag is way too generic. It is not clear that the
> accounting is KMEMCG related.
The memory controller is the (primary) component that accounts
physical memory allocations in the kernel, so I don't see how this
would be ambiguous in any way.
> __GFP_NO_KMEMCG sounds better?
I think that's much worse. I would prefer communicating the desired
behavior directly instead of having to derive it from a subsystem
name.
(And KMEMCG should not even be a term, it's all just the memory
controller, i.e. memcg.)
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Weiner <hannes@cmpxchg.org>
To: Michal Hocko <mhocko@suse.cz>
Cc: Vladimir Davydov <vdavydov@parallels.com>,
Andrew Morton <akpm@linux-foundation.org>,
Tejun Heo <tj@kernel.org>, Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Greg Thelen <gthelen@google.com>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] gfp: add __GFP_NOACCOUNT
Date: Wed, 6 May 2015 09:16:22 -0400 [thread overview]
Message-ID: <20150506131622.GA4629@cmpxchg.org> (raw)
In-Reply-To: <20150506115941.GH14550@dhcp22.suse.cz>
On Wed, May 06, 2015 at 01:59:41PM +0200, Michal Hocko wrote:
> On Tue 05-05-15 12:45:42, Vladimir Davydov wrote:
> > Not all kmem allocations should be accounted to memcg. The following
> > patch gives an example when accounting of a certain type of allocations
> > to memcg can effectively result in a memory leak.
>
> > This patch adds the __GFP_NOACCOUNT flag which if passed to kmalloc
> > and friends will force the allocation to go through the root
> > cgroup. It will be used by the next patch.
>
> The name of the flag is way too generic. It is not clear that the
> accounting is KMEMCG related.
The memory controller is the (primary) component that accounts
physical memory allocations in the kernel, so I don't see how this
would be ambiguous in any way.
> __GFP_NO_KMEMCG sounds better?
I think that's much worse. I would prefer communicating the desired
behavior directly instead of having to derive it from a subsystem
name.
(And KMEMCG should not even be a term, it's all just the memory
controller, i.e. memcg.)
--
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: Johannes Weiner <hannes@cmpxchg.org>
To: Michal Hocko <mhocko@suse.cz>
Cc: Vladimir Davydov <vdavydov@parallels.com>,
Andrew Morton <akpm@linux-foundation.org>,
Tejun Heo <tj@kernel.org>, Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Greg Thelen <gthelen@google.com>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] gfp: add __GFP_NOACCOUNT
Date: Wed, 6 May 2015 09:16:22 -0400 [thread overview]
Message-ID: <20150506131622.GA4629@cmpxchg.org> (raw)
In-Reply-To: <20150506115941.GH14550@dhcp22.suse.cz>
On Wed, May 06, 2015 at 01:59:41PM +0200, Michal Hocko wrote:
> On Tue 05-05-15 12:45:42, Vladimir Davydov wrote:
> > Not all kmem allocations should be accounted to memcg. The following
> > patch gives an example when accounting of a certain type of allocations
> > to memcg can effectively result in a memory leak.
>
> > This patch adds the __GFP_NOACCOUNT flag which if passed to kmalloc
> > and friends will force the allocation to go through the root
> > cgroup. It will be used by the next patch.
>
> The name of the flag is way too generic. It is not clear that the
> accounting is KMEMCG related.
The memory controller is the (primary) component that accounts
physical memory allocations in the kernel, so I don't see how this
would be ambiguous in any way.
> __GFP_NO_KMEMCG sounds better?
I think that's much worse. I would prefer communicating the desired
behavior directly instead of having to derive it from a subsystem
name.
(And KMEMCG should not even be a term, it's all just the memory
controller, i.e. memcg.)
next prev parent reply other threads:[~2015-05-06 13:16 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 9:45 [PATCH 1/2] gfp: add __GFP_NOACCOUNT Vladimir Davydov
2015-05-05 16:07 ` Vladimir Davydov
2015-05-05 9:45 ` Vladimir Davydov
2015-05-05 9:45 ` Vladimir Davydov
2015-05-06 11:59 ` Michal Hocko
2015-05-06 11:59 ` Michal Hocko
[not found] ` <20150506115941.GH14550-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2015-05-06 12:24 ` Vladimir Davydov
2015-05-06 12:24 ` Vladimir Davydov
2015-05-06 12:24 ` Vladimir Davydov
2015-05-06 12:35 ` Michal Hocko
2015-05-06 12:35 ` Michal Hocko
2015-05-06 12:35 ` Michal Hocko
2015-05-06 13:25 ` Vladimir Davydov
2015-05-06 13:25 ` Vladimir Davydov
2015-05-06 13:55 ` Michal Hocko
2015-05-06 13:55 ` Michal Hocko
2015-05-06 13:55 ` Michal Hocko
2015-05-06 14:29 ` Vladimir Davydov
2015-05-06 14:29 ` Vladimir Davydov
2015-05-06 14:46 ` Michal Hocko
2015-05-06 14:46 ` Michal Hocko
2015-05-06 14:46 ` Michal Hocko
2015-05-06 13:16 ` Johannes Weiner [this message]
2015-05-06 13:16 ` Johannes Weiner
2015-05-06 13:16 ` Johannes Weiner
[not found] ` <20150506131622.GA4629-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
2015-05-06 13:46 ` Michal Hocko
2015-05-06 13:46 ` Michal Hocko
2015-05-06 13:46 ` Michal Hocko
2015-05-06 15:00 ` Johannes Weiner
2015-05-06 15:00 ` Johannes Weiner
[not found] ` <fdf631b3fa95567a830ea4f3e19d0b3b2fc99662.1430819044.git.vdavydov-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2015-05-05 9:45 ` [PATCH 2/2] kernfs: do not account ino_ida allocations to memcg Vladimir Davydov
2015-05-05 16:07 ` Vladimir Davydov
2015-05-05 9:45 ` Vladimir Davydov
2015-05-05 9:45 ` Vladimir Davydov
2015-05-05 13:45 ` Tejun Heo
2015-05-05 13:45 ` Tejun Heo
2015-05-05 16:04 ` Vladimir Davydov
2015-05-05 16:04 ` Vladimir Davydov
2015-05-06 14:58 ` [PATCH 1/2] gfp: add __GFP_NOACCOUNT Michal Hocko
2015-05-06 14:58 ` Michal Hocko
2015-05-06 14:58 ` Michal Hocko
2015-05-06 16:35 ` [PATCH v2] " Vladimir Davydov
2015-05-06 16:35 ` Vladimir Davydov
2015-05-06 16:35 ` Vladimir Davydov
2015-05-06 17:52 ` [PATCH 1/2] " Johannes Weiner
2015-05-06 17:52 ` Johannes Weiner
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=20150506131622.GA4629@cmpxchg.org \
--to=hannes-druugvl0lcnafugrpc6u6w@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=cl-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org \
--cc=gthelen-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=iamjoonsoo.kim-Hm3cg6mZ9cc@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=mhocko-AlSwsSmVLrQ@public.gmane.org \
--cc=penberg-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=rientjes-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=vdavydov-bzQdu9zFT3WakBO8gow8eQ@public.gmane.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.