From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, T_DKIMWL_WL_HIGH,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AF12DC28CC5 for ; Wed, 5 Jun 2019 04:14:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 7957720866 for ; Wed, 5 Jun 2019 04:14:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1559708060; bh=edj9xHB7N4qyQuNAjukxlep6ykAdTpTJSbDVobW9eyE=; h=Date:From:To:Cc:Subject:In-Reply-To:References:List-ID:From; b=bsLx2KDHg+0mfe6U0vS3bB8cQ06FcsNrfNTIUJbgxBHvLIlkXSWhvfFfnnBEQAIab Be5EMoQbg2uLtYQKl+MCa5iHsoaTmOt7cVavTZ5KzbAulYkSE+V/YKEC9tozs/jLOF k1t1UmPQRXGnIe430FK2QuiZ58JOh2/rh0PRNoHc= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726573AbfFEEOT (ORCPT ); Wed, 5 Jun 2019 00:14:19 -0400 Received: from mail.kernel.org ([198.145.29.99]:46354 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725268AbfFEEOT (ORCPT ); Wed, 5 Jun 2019 00:14:19 -0400 Received: from localhost.localdomain (c-73-231-172-41.hsd1.ca.comcast.net [73.231.172.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 8AA582083E; Wed, 5 Jun 2019 04:14:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1559708058; bh=edj9xHB7N4qyQuNAjukxlep6ykAdTpTJSbDVobW9eyE=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=2YKq0Ebk1+cB6qr58E9NAgemhGn6EHb0HDouxp1tY+7raXsMRSeotQrm+P5lIPs1v L6mN1jBg0wqjF15WZC+qr2bLNQOb6kr4HaRV+v0csG/ttAlC9TpwLb3UFcUAR0mm1f QiE+/S8AFSkUzLizIkatXvaSNq3NKDwY8kGiTTn8= Date: Tue, 4 Jun 2019 21:14:18 -0700 From: Andrew Morton To: Roman Gushchin Cc: , , , Johannes Weiner , Shakeel Butt , Vladimir Davydov , Waiman Long Subject: Re: [PATCH v6 00/10] mm: reparent slab memory on cgroup removal Message-Id: <20190604211418.70d178253550d96da46cee21@linux-foundation.org> In-Reply-To: <20190605024454.1393507-1-guro@fb.com> References: <20190605024454.1393507-1-guro@fb.com> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 4 Jun 2019 19:44:44 -0700 Roman Gushchin wrote: > So instead of trying to find a maybe non-existing balance, let's do reparent > the accounted slabs to the parent cgroup on cgroup removal. s/slabs/slab caches/. Take more care with the terminology, please... > There is a bonus: currently we do release empty kmem_caches on cgroup > removal, however all other are waiting for the releasing of the memory cgroup. > These refactorings allow kmem_caches to be released as soon as they > become inactive and free. Unclear. s/All other/releasing of all non-empty slab caches depends upon the releasing/ I think?