From: Vladimir Davydov <vdavydov@parallels.com>
To: Michal Hocko <mhocko@suse.cz>, Johannes Weiner <hannes@cmpxchg.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [mmotm:master 143/283] mm/slab.c:3260:4: error: implicit declaration of function 'slab_free'
Date: Thu, 6 Nov 2014 12:28:49 +0300 [thread overview]
Message-ID: <20141106092849.GC4839@esperanza> (raw)
In-Reply-To: <20141106090845.GA17744@dhcp22.suse.cz>
Hi Michal,
On Thu, Nov 06, 2014 at 10:08:45AM +0100, Michal Hocko wrote:
> I have encountered the same error as well. We need to move the forward
> declaration up outside of CONFIG_NUMA:
Yes, that's my fault, I'm sorry. Thank you for fixing this.
BTW what do you think about the whole patch set that introduced it -
https://lkml.org/lkml/2014/11/3/781 - w/o diving deeply into details,
just by looking at the general idea described in the cover letter?
Does it look like acceptable to you that a cgroup can get a cache with
some objects left from the previous user? Or do you think it's better to
give each cgroup its own cache as it used to be before and introduce
cache auto-destruction somehow (that would be tricky though, but
possible)? Or perhaps it'd be better to get rid of per-memcg caches
altogether and share the same kmem cache for all kmem allocations
keeping a pointer to the owner memcg in each kmem object?
I'd really appreciate if you or Johannes could share your thoughts on
it, because I'm afraid I can do something everybody will regret about in
the future...
Thanks,
Vladimir
--
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:[~2014-11-06 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 1:16 [mmotm:master 143/283] mm/slab.c:3260:4: error: implicit declaration of function 'slab_free' kbuild test robot
2014-11-06 9:08 ` Michal Hocko
2014-11-06 9:28 ` Vladimir Davydov [this message]
2014-11-06 14:05 ` Michal Hocko
2014-11-06 14:30 ` Vladimir Davydov
2014-11-06 14:33 ` Michal Hocko
2014-11-06 9:13 ` 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=20141106092849.GC4839@esperanza \
--to=vdavydov@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.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;
as well as URLs for NNTP newsgroup(s).