Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp2847440imm; Sat, 12 May 2018 22:15:39 -0700 (PDT) X-Google-Smtp-Source: AB8JxZozy151ktuV0RiZ8jg2GdCw9+U9qEcKwoXvlN5+ZBX1k5naVbFkdG/jE4osWY3E6R2KqJDQ X-Received: by 2002:a65:4b8d:: with SMTP id t13-v6mr3072801pgq.53.1526188539321; Sat, 12 May 2018 22:15:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526188539; cv=none; d=google.com; s=arc-20160816; b=ZAERSLkQRvkeL5vhdr2XST9h73SXYHYUcWGaz2yFOXu0xTWzw/Xsjq9jOZoP/j3Sfs pedPnXTd5Hlqqs7XNWa40I1T5xoSI0WuI2mQo/2gHIEnLkZD8ddO64JCBTQ7vHDfBmxs rYB47B4j7BVxaIiJ4H9O5D5SJIFVawfcqayvpiLOtOOkp8/ROm9MELHWLq+3ey4lnF6n V1KCUDcvxqFhSDOVh3+G4l0jwk5eml+F634uXG7m1gA8081rfXXRK3Fj1t+N2v9rdEOj 9J5KiZ8CvRGHf7klGNN5wanxfQPKHsJwO4q0tFKXcWIt7M/3RgGWg5fGTMLFS39mBFzt wHgQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature:arc-authentication-results; bh=lSW09Jr5T1lwfnRps0av0UlmKX7MGtOkP9faxXCDupA=; b=ax7YdxaHhQ5YGskEUsmiUyqUuo6eiBndrY4fbaFlwzfXCEVYujhF/PZjP9l370upOB jPyQy70eKfK/r7cdp8GVSacNWRYOEkIny5dEa4Yu5FURoDH49JR+4IEqIrdt9+xmptmz qia1q0Mjsr5XfCGxLcwQ26u9JhbSnExBj6oYfy10yGJl9sZeSRcY8F2lQb5LUPWMTec0 R1YQw0PROYNnoPDPSgRiTPlXwFXyVhbiLQRYCsdLOjKWVnP4ZpKTT66IsbLIUwrpxfWj PUU4+XGPxoSuAj5uPEdfajZo8GtvKdPdd3okV+qjUYKbJ9YfomCSeuoqxiOSRLOIffy0 6DXw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=RijV6F04; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p8-v6si6548733plk.441.2018.05.12.22.15.22; Sat, 12 May 2018 22:15:39 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=RijV6F04; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750985AbeEMFPP (ORCPT + 99 others); Sun, 13 May 2018 01:15:15 -0400 Received: from mail-pf0-f194.google.com ([209.85.192.194]:33337 "EHLO mail-pf0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750850AbeEMFPN (ORCPT ); Sun, 13 May 2018 01:15:13 -0400 Received: by mail-pf0-f194.google.com with SMTP id a20-v6so551488pfo.0 for ; Sat, 12 May 2018 22:15:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=lSW09Jr5T1lwfnRps0av0UlmKX7MGtOkP9faxXCDupA=; b=RijV6F04p6VTl98COaWguiDLH8HHbKt96doRUG/aa/SysFMjoPDhdTdtLC/TecfLO6 dJwoIegBhLXlt89wwDjUx8WR/JjSkosXt2Mut5hzsbr7uUQgaJj/SID5NIFLDHREexDj Cvxc6O8RdQZhYzcYX8nx+v5+n0t8qTxTPO89776NoHna9S7LJ3Y/iII8kLaVf4YOzx61 LIi9EPg4LSZIrvhUsXzbiEpi7gAqYt6eFXqS8Bf5ZYU0QjrIXms4ViVTgLQiVPF6GvTr GoIL3UpJjwJXoE3ATK5IF66ytoAAvhSCJpJq8S2Rhef9DB2IvkLgypCF20Ql8Ki5ON0x QuJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=lSW09Jr5T1lwfnRps0av0UlmKX7MGtOkP9faxXCDupA=; b=PfBU4lB4h0jnyP7uy/SjofFv37t3ZCKwNPjZUFbl+UvRmyLYWXW0w1zbhr4xqg9JPJ Bbmb9g60f3wFp4/yrTQwImHSft78DauONsvKYeWyOLurfZXxU/sOK1wgsAJPx4e6/muu DTUerAexDZZMlW/zvvhT90Io3A70q6TZsuI+5orfTKFLkGnASZYgYMR87ABaBPJ0vphg alLKpMh2W9nAJ+bW1D3esuRYcF3PIxtKvB/SFuWUXeuDXptzishRT+5iITl7btXMmSMc K1tasrDrepWRO3mxe9euRH9i6Ml/W/Pqgsou7xMBXB1Mk9bB1f8kzASxQPi3XhANSGbE D2Fw== X-Gm-Message-State: ALKqPweglFZCPiq4syQQ15W0o4yqhVCmFvuxs293dkPYsYPWqCupKFDu Wkrl7Qtpf3XnMt8JoF6M1Wg= X-Received: by 2002:a62:4544:: with SMTP id s65-v6mr5394046pfa.150.1526188513304; Sat, 12 May 2018 22:15:13 -0700 (PDT) Received: from esperanza ([216.9.110.7]) by smtp.gmail.com with ESMTPSA id u86-v6sm15951980pfg.71.2018.05.12.22.15.11 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 12 May 2018 22:15:12 -0700 (PDT) Date: Sun, 13 May 2018 08:15:09 +0300 From: Vladimir Davydov To: Kirill Tkhai Cc: akpm@linux-foundation.org, shakeelb@google.com, viro@zeniv.linux.org.uk, hannes@cmpxchg.org, mhocko@kernel.org, tglx@linutronix.de, pombredanne@nexb.com, stummala@codeaurora.org, gregkh@linuxfoundation.org, sfr@canb.auug.org.au, guro@fb.com, mka@chromium.org, penguin-kernel@I-love.SAKURA.ne.jp, chris@chris-wilson.co.uk, longman@redhat.com, minchan@kernel.org, ying.huang@intel.com, mgorman@techsingularity.net, jbacik@fb.com, linux@roeck-us.net, linux-kernel@vger.kernel.org, linux-mm@kvack.org, willy@infradead.org, lirongqing@baidu.com, aryabinin@virtuozzo.com Subject: Re: [PATCH v5 01/13] mm: Assign id to every memcg-aware shrinker Message-ID: <20180513051509.df2tcmbhxn3q2fp7@esperanza> References: <152594582808.22949.8353313986092337675.stgit@localhost.localdomain> <152594593798.22949.6730606876057040426.stgit@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <152594593798.22949.6730606876057040426.stgit@localhost.localdomain> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 10, 2018 at 12:52:18PM +0300, Kirill Tkhai wrote: > The patch introduces shrinker::id number, which is used to enumerate > memcg-aware shrinkers. The number start from 0, and the code tries > to maintain it as small as possible. > > This will be used as to represent a memcg-aware shrinkers in memcg > shrinkers map. > > Since all memcg-aware shrinkers are based on list_lru, which is per-memcg > in case of !SLOB only, the new functionality will be under MEMCG && !SLOB > ifdef (symlinked to CONFIG_MEMCG_SHRINKER). Using MEMCG && !SLOB instead of introducing a new config option was done deliberately, see: http://lkml.kernel.org/r/20151210202244.GA4809@cmpxchg.org I guess, this doesn't work well any more, as there are more and more parts depending on kmem accounting, like shrinkers. If you really want to introduce a new option, I think you should call it CONFIG_MEMCG_KMEM and use it consistently throughout the code instead of MEMCG && !SLOB. And this should be done in a separate patch. > diff --git a/fs/super.c b/fs/super.c > index 122c402049a2..16c153d2f4f1 100644 > --- a/fs/super.c > +++ b/fs/super.c > @@ -248,6 +248,9 @@ static struct super_block *alloc_super(struct file_system_type *type, int flags, > s->s_time_gran = 1000000000; > s->cleancache_poolid = CLEANCACHE_NO_POOL; > > +#ifdef CONFIG_MEMCG_SHRINKER > + s->s_shrink.id = -1; > +#endif No point doing that - you are going to overwrite the id anyway in prealloc_shrinker(). > s->s_shrink.seeks = DEFAULT_SEEKS; > s->s_shrink.scan_objects = super_cache_scan; > s->s_shrink.count_objects = super_cache_count; > diff --git a/mm/vmscan.c b/mm/vmscan.c > index 10c8a38c5eef..d691beac1048 100644 > --- a/mm/vmscan.c > +++ b/mm/vmscan.c > @@ -169,6 +169,47 @@ unsigned long vm_total_pages; > static LIST_HEAD(shrinker_list); > static DECLARE_RWSEM(shrinker_rwsem); > > +#ifdef CONFIG_MEMCG_SHRINKER > +static DEFINE_IDR(shrinker_idr); > + > +static int prealloc_memcg_shrinker(struct shrinker *shrinker) > +{ > + int id, ret; > + > + down_write(&shrinker_rwsem); > + ret = id = idr_alloc(&shrinker_idr, shrinker, 0, 0, GFP_KERNEL); > + if (ret < 0) > + goto unlock; > + shrinker->id = id; > + ret = 0; > +unlock: > + up_write(&shrinker_rwsem); > + return ret; > +} > + > +static void del_memcg_shrinker(struct shrinker *shrinker) Nit: IMO unregister_memcg_shrinker() would be a better name as it matches unregister_shrinker(), just like prealloc_memcg_shrinker() matches prealloc_shrinker(). > +{ > + int id = shrinker->id; > + > + if (id < 0) > + return; Nit: I think this should be BUG_ON(id >= 0) as this function is only called for memcg-aware shrinkers AFAICS. > + > + down_write(&shrinker_rwsem); > + idr_remove(&shrinker_idr, id); > + up_write(&shrinker_rwsem); > + shrinker->id = -1; > +}