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;
Date:   Fri, 10 Sep 2021 08:01:50 +0200
From:   Greg KH <gregkh@linuxfoundation.org>
To:     "taoyi.ty" <escape@linux.alibaba.com>
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: <YTr0zvythCIJk4Xb@kroah.com>
References: <cover.1631102579.git.escape@linux.alibaba.com>
 <YTiugxO0cDge47x6@kroah.com>
 <a0c67d71-8045-d8b6-40c2-39f2603ec7c1@linux.alibaba.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <a0c67d71-8045-d8b6-40c2-39f2603ec7c1@linux.alibaba.com>
Precedence: bulk

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