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=-6.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no 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 F404FC433EF for ; Fri, 10 Sep 2021 06:02:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D506E611C3 for ; Fri, 10 Sep 2021 06:02:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230521AbhIJGDY (ORCPT ); Fri, 10 Sep 2021 02:03:24 -0400 Received: from mail.kernel.org ([198.145.29.99]:55394 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230417AbhIJGDX (ORCPT ); Fri, 10 Sep 2021 02:03:23 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 6245B6113A; Fri, 10 Sep 2021 06:02:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1631253733; bh=kWhJlIC/1vHbeFhKoaxwk/xnuUNuDuDMWv8UUrP4zwU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=GKOXggWLy1L4eUBaHMMLpMRIcYzEKuAxNZ96kGhtbWEkketIVT4i+VcUb2tvEfQmq /8SEFpiR/3lcdZhmoSCeEkWsx74JVPuFkg6E8bZ7Xu4fBKzz5jPK/HTt6GkMJXJdTL vN42zrZNw87OmLaDErMrRv0IPf47T4dVNRQ1N7Ik= Date: Fri, 10 Sep 2021 08:01:50 +0200 From: Greg KH To: "taoyi.ty" Cc: tj@kernel.org, lizefan.x@bytedance.com, hannes@cmpxchg.org, mcgrof@kernel.org, keescook@chromium.org, yzaikin@google.com, linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, linux-fsdevel@vger.kernel.org, shanpeic@linux.alibaba.com Subject: Re: [RFC PATCH 0/2] support cgroup pool in v1 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 10, 2021 at 10:11:53AM +0800, taoyi.ty wrote: > On 2021/9/8 下午8:37, Greg KH wrote: > > > Perhaps you shouldn't be creating that many containers all at once? > > What normal workload requires this? > > Thank you for your reply. > > > The scenario is the function computing of the public > > cloud. Each instance of function computing will be > > allocated about 0.1 core cpu and 100M memory. On > > a high-end server, for example, 104 cores and 384G, > > it is normal to create hundreds of containers at the > > same time if burst of requests comes. So it is a resource management issue on your side, right? Perhaps stagger the creation of new containers to allow the overall creation time to be less? thanks, greg k-h From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: [RFC PATCH 0/2] support cgroup pool in v1 Date: Fri, 10 Sep 2021 08:01:50 +0200 Message-ID: References: Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1631253733; bh=kWhJlIC/1vHbeFhKoaxwk/xnuUNuDuDMWv8UUrP4zwU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=GKOXggWLy1L4eUBaHMMLpMRIcYzEKuAxNZ96kGhtbWEkketIVT4i+VcUb2tvEfQmq /8SEFpiR/3lcdZhmoSCeEkWsx74JVPuFkg6E8bZ7Xu4fBKzz5jPK/HTt6GkMJXJdTL vN42zrZNw87OmLaDErMrRv0IPf47T4dVNRQ1N7Ik= Content-Disposition: inline In-Reply-To: List-ID: Content-Type: text/plain; charset="utf-8" To: "taoyi.ty" Cc: tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, lizefan.x-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org, hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org, mcgrof-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org, yzaikin-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, shanpeic-KPsoFbNs7GizrGE5bRqYAgC/G2K4zDHf@public.gmane.org On Fri, Sep 10, 2021 at 10:11:53AM +0800, taoyi.ty wrote: > On 2021/9/8 下午8:37, Greg KH wrote: > > > Perhaps you shouldn't be creating that many containers all at once? > > What normal workload requires this? > > Thank you for your reply. > > > The scenario is the function computing of the public > > cloud. Each instance of function computing will be > > allocated about 0.1 core cpu and 100M memory. On > > a high-end server, for example, 104 cores and 384G, > > it is normal to create hundreds of containers at the > > same time if burst of requests comes. So it is a resource management issue on your side, right? Perhaps stagger the creation of new containers to allow the overall creation time to be less? thanks, greg k-h