Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp525728pxk; Wed, 2 Sep 2020 08:00:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw3CyfBZvsG6Tq6q/QgMY41bpIuT7fmUp0oQYD2pDWoMnAVPSibn1hlRMbvQjrtErG9ns7y X-Received: by 2002:a17:906:aac7:: with SMTP id kt7mr404315ejb.548.1599058851986; Wed, 02 Sep 2020 08:00:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1599058851; cv=none; d=google.com; s=arc-20160816; b=eJPApinl0GqzcwBrKi92GbHN391Ur4u8KNBsCJ9kgekGECfrsuox6D15UErjTrlMLd AKj1ejbTwbLilzvITmHrmSkN7zBNuawGy9zmm1PwrfyrPe5c8gFfxq6hfE6PRfRxC4z8 vbb7OFvk0r4u05r4SYNJHbcYk5JRxoo/3HtnEl+aQSe7+pkph5dFGIREeEo3DvpdsspA BHdB1gpoX+CfcdiveaCwMwCnCGdbzIjZkvVoJPftaKEfdpx/rvMR92hMuMmYr9N/SdHP cALW94xBdsaxC/7pjNkcdaU5T6whsLe6dkp2i9uxlX/65GQnOfxH/WLuvamO9TfnOTIx ft9Q== 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; bh=Q6/zbrNW3sjUdXi5AtLoM5PJtB+f2cMX4dKgZgXNUXY=; b=ifmHkKLMnn5Xy1x5teCIaVlo0L1J7sQEmA+vkyJQWt2UGihyqdv/A2Yw12RXJ6d3qg 6dnp2E4VovnzKBBPgxZYIraR06C6lFmAhTYDdoT/HaKegDoo9KQN0CldoWIKC8T+AGyl dDbqEhU7Y/BZ8i+ttOXCnvslWoBc5zvbiZlcy9fMZOrzdS8oE66mJkRzw9SJFpvzLDux +21i4AaQKhEJI5Y414+7toytf5yvVGOBK1NKe2twjL3sOM3v5SzeAB1eaxhnkZb4aMx5 8cNuWXmwh1PTeyBFt4BJ5KXKutXh7i1FzCBrvLXP2mZlS1jZeLPFInV2XTtV92afrUp/ DdGA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id mh25si2533014ejb.568.2020.09.02.08.00.28; Wed, 02 Sep 2020 08:00:51 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727986AbgIBO67 (ORCPT + 99 others); Wed, 2 Sep 2020 10:58:59 -0400 Received: from mx2.suse.de ([195.135.220.15]:46544 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726355AbgIBNxQ (ORCPT ); Wed, 2 Sep 2020 09:53:16 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 77D7EB630; Wed, 2 Sep 2020 13:53:00 +0000 (UTC) Date: Wed, 2 Sep 2020 15:52:58 +0200 From: Michal Hocko To: Pavel Tatashin Cc: Vlastimil Babka , Roman Gushchin , Bharata B Rao , "linux-mm@kvack.org" , Andrew Morton , Johannes Weiner , Shakeel Butt , Vladimir Davydov , "linux-kernel@vger.kernel.org" , Kernel Team , Yafang Shao , stable , Linus Torvalds , Sasha Levin , Greg Kroah-Hartman , David Hildenbrand Subject: Re: [PATCH v2 00/28] The new cgroup slab memory controller Message-ID: <20200902135258.GH4617@dhcp22.suse.cz> References: <20200127173453.2089565-1-guro@fb.com> <20200130020626.GA21973@in.ibm.com> <20200130024135.GA14994@xps.DHCP.thefacebook.com> <20200813000416.GA1592467@carbon.dhcp.thefacebook.com> <6469324e-afa2-18b4-81fb-9e96466c1bf3@suse.cz> <20200902113204.GD4617@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 02-09-20 08:53:49, Pavel Tatashin wrote: > On Wed, Sep 2, 2020 at 7:32 AM Michal Hocko wrote: > > > > On Wed 02-09-20 11:53:00, Vlastimil Babka wrote: > > > >> > > Thread #2: ccs killer kthread > > > >> > > css_killed_work_fn > > > >> > > cgroup_mutex <- Grab this Mutex > > > >> > > mem_cgroup_css_offline > > > >> > > memcg_offline_kmem.part > > > >> > > memcg_deactivate_kmem_caches > > > >> > > get_online_mems > > > >> > > mem_hotplug_lock <- waits for Thread#1 to get read access > > > > And one more thing. THis has been brought up several times already. > > Maybe I have forgoten but why do we take hotplug locks in this path in > > the first place? Memory hotplug notifier takes slab_mutex so this > > shouldn't be really needed. > > Good point, it seems this lock can be completely removed from > memcg_deactivate_kmem_caches I am pretty sure we have discussed that in the past. But I do not remember the outcome. Either we have concluded that this is indeed the case but nobody came up with a patch or we have hit some obscure issue... Maybe David/Roman rememeber more than I do. -- Michal Hocko SUSE Labs