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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7CCC5C433EF for ; Thu, 19 May 2022 16:53:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242209AbiESQxg (ORCPT ); Thu, 19 May 2022 12:53:36 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50656 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242206AbiESQxd (ORCPT ); Thu, 19 May 2022 12:53:33 -0400 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 676CC66C84; Thu, 19 May 2022 09:53:28 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 08AD521BA8; Thu, 19 May 2022 16:53:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1652979207; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=6frXTBgzGRsjQpEWOm3xYp6acz/9cACY818c3GjmbTE=; b=aU4Zz5L96bfOjnVSWwfUl/ZOl+pAHsxcqe088kJSSjOLa4Lo/g4x6rXHcEeW56lZA8rXfn Zd72o8ccBgsUKXmWVf+tFT7ICCA3Xn7X1C1Dh3B73jS5NH59GNa1+Osny2pwZrHT6DYSl8 I73RnhMuNCm9ZcgAXED12k4VMQysZuA= Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id CB63913456; Thu, 19 May 2022 16:53:26 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id mAutMAZ2hmJHCgAAMHmgww (envelope-from ); Thu, 19 May 2022 16:53:26 +0000 Date: Thu, 19 May 2022 18:53:25 +0200 From: Michal =?iso-8859-1?Q?Koutn=FD?= To: Vasily Averin Cc: Roman Gushchin , Shakeel Butt , kernel@openvz.org, linux-kernel@vger.kernel.org, Vlastimil Babka , Michal Hocko , cgroups@vger.kernel.org Subject: Re: [PATCH 3/4] memcg: enable accounting for struct cgroup Message-ID: <20220519165325.GA2434@blackbody.suse.cz> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 13, 2022 at 06:52:12PM +0300, Vasily Averin wrote: > Creating each new cgroup allocates 4Kb for struct cgroup. This is the > largest memory allocation in this scenario and is epecially important > for small VMs with 1-2 CPUs. What do you mean by this argument? (On bigger irons, the percpu components becomes dominant, e.g. struct cgroup_rstat_cpu.) Thanks, Michal From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal =?iso-8859-1?Q?Koutn=FD?= Subject: Re: [PATCH 3/4] memcg: enable accounting for struct cgroup Date: Thu, 19 May 2022 18:53:25 +0200 Message-ID: <20220519165325.GA2434@blackbody.suse.cz> References: Mime-Version: 1.0 Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1652979207; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=6frXTBgzGRsjQpEWOm3xYp6acz/9cACY818c3GjmbTE=; b=aU4Zz5L96bfOjnVSWwfUl/ZOl+pAHsxcqe088kJSSjOLa4Lo/g4x6rXHcEeW56lZA8rXfn Zd72o8ccBgsUKXmWVf+tFT7ICCA3Xn7X1C1Dh3B73jS5NH59GNa1+Osny2pwZrHT6DYSl8 I73RnhMuNCm9ZcgAXED12k4VMQysZuA= Content-Disposition: inline In-Reply-To: List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Vasily Averin Cc: Roman Gushchin , Shakeel Butt , kernel-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Vlastimil Babka , Michal Hocko , cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org On Fri, May 13, 2022 at 06:52:12PM +0300, Vasily Averin wrote: > Creating each new cgroup allocates 4Kb for struct cgroup. This is the > largest memory allocation in this scenario and is epecially important > for small VMs with 1-2 CPUs. What do you mean by this argument? (On bigger irons, the percpu components becomes dominant, e.g. struct cgroup_rstat_cpu.) Thanks, Michal