From: Andrey Wagin <avagin@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, cgroups@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Glauber Costa <glommer@openvz.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.cz>,
Balbir Singh <bsingharora@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [PATCH] kmemcg: don't allocate extra memory for root memcg_cache_params
Date: Thu, 15 Aug 2013 09:13:11 +0400 [thread overview]
Message-ID: <CANaxB-x7-H6yeTJ4=F4bJW=UgvvyUD_200wZG-gz9-3wYSh4hg@mail.gmail.com> (raw)
In-Reply-To: <20130814134710.ff123b0ea802efa7261d7e26@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 2258 bytes --]
2013/8/15 Andrew Morton <akpm@linux-foundation.org>
> On Wed, 14 Aug 2013 14:31:21 +0400 Andrey Vagin <avagin@openvz.org> wrote:
>
> > The memcg_cache_params structure contains the common part and the union,
> > which represents two different types of data: one for root cashes and
> > another for child caches.
> >
> > The size of child data is fixed. The size of the memcg_caches array is
> > calculated in runtime.
> >
> > Currently the size of memcg_cache_params for root caches is calculated
> > incorrectly, because it includes the size of parameters for child caches.
> >
> > ssize_t size = memcg_caches_array_size(num_groups);
> > size *= sizeof(void *);
> >
> > size += sizeof(struct memcg_cache_params);
> >
> > ...
> >
> > --- a/mm/memcontrol.c
> > +++ b/mm/memcontrol.c
> > @@ -3140,7 +3140,7 @@ int memcg_update_cache_size(struct kmem_cache *s,
> int num_groups)
> > ssize_t size = memcg_caches_array_size(num_groups);
> >
> > size *= sizeof(void *);
> > - size += sizeof(struct memcg_cache_params);
> > + size += sizeof(offsetof(struct memcg_cache_params,
> memcg_caches));
>
> This looks wrong. offsetof() returns size_t, so this is equivalent to
>
> size += sizeof(size_t);
>
sizeof doesn't have to be here. I will resend this patch. Thanks.
size += offsetof(struct memcg_cache_params, memcg_caches)
> > s->memcg_params = kzalloc(size, GFP_KERNEL);
> > if (!s->memcg_params) {
> > @@ -3183,13 +3183,16 @@ int memcg_update_cache_size(struct kmem_cache
> *s, int num_groups)
> > int memcg_register_cache(struct mem_cgroup *memcg, struct kmem_cache *s,
> > struct kmem_cache *root_cache)
> > {
> > - size_t size = sizeof(struct memcg_cache_params);
> > + size_t size;
> >
> > if (!memcg_kmem_enabled())
> > return 0;
> >
> > - if (!memcg)
> > + if (!memcg) {
> > + size = offsetof(struct memcg_cache_params, memcg_caches);
> > size += memcg_limited_groups_array_size * sizeof(void *);
> > + } else
> > + size = sizeof(struct memcg_cache_params);
> >
> > s->memcg_params = kzalloc(size, GFP_KERNEL);
> > if (!s->memcg_params)
>
>
[-- Attachment #2: Type: text/html, Size: 3320 bytes --]
prev parent reply other threads:[~2013-08-15 5:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 10:31 Andrey Vagin
2013-08-14 20:47 ` Andrew Morton
2013-08-15 5:13 ` Andrey Wagin [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='CANaxB-x7-H6yeTJ4=F4bJW=UgvvyUD_200wZG-gz9-3wYSh4hg@mail.gmail.com' \
--to=avagin@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=glommer@openvz.org \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
/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