Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752237AbbKKQHh (ORCPT ); Wed, 11 Nov 2015 11:07:37 -0500 Received: from mx2.parallels.com ([199.115.105.18]:57806 "EHLO mx2.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750961AbbKKQHf (ORCPT ); Wed, 11 Nov 2015 11:07:35 -0500 Date: Wed, 11 Nov 2015 19:07:19 +0300 From: Vladimir Davydov To: Tejun Heo CC: Andrew Morton , Johannes Weiner , Michal Hocko , Greg Thelen , Christoph Lameter , Pekka Enberg , David Rientjes , Joonsoo Kim , , , Subject: Re: [PATCH v2 4/6] slab: add SLAB_ACCOUNT flag Message-ID: <20151111160719.GX31308@esperanza> References: <1ce23e932ea53f47a3376de90b21a9db8293bd6c.1447172835.git.vdavydov@virtuozzo.com> <20151110183808.GB13740@mtj.duckdns.org> <20151110185401.GW31308@esperanza> <20151111155450.GB6246@mtj.duckdns.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20151111155450.GB6246@mtj.duckdns.org> X-ClientProxiedBy: US-EXCH.sw.swsoft.com (10.255.249.47) To US-EXCH2.sw.swsoft.com (10.255.249.46) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1293 Lines: 29 On Wed, Nov 11, 2015 at 10:54:50AM -0500, Tejun Heo wrote: > Hello, > > On Tue, Nov 10, 2015 at 09:54:01PM +0300, Vladimir Davydov wrote: > > > Am I correct in thinking that we should eventually be able to removed > > > __GFP_ACCOUNT and that only caches explicitly marked with SLAB_ACCOUNT > > > would need to be handled by kmemcg? > > > > Don't think so, because sometimes we want to account kmalloc. > > I'm kinda skeptical about that because if those allocations are > occassional by nature, we don't care and if there can be a huge number > of them, splitting them into a separate cache makes sense. I think it > makes sense to pin down exactly which caches are memcg managed. That > has the potential to simplify the involved code path and shave off a > small bit of hot path overhead. What about external_name allocation in __d_alloc? Is it occasional? Depends on the workload I guess. Can we create a separate cache for it? No, because its size is variable. There are other things like that, e.g. pipe_buffer array. Thanks, Vladimir -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/