linux-kernel - Re: [RFC PATCH 0/2] support cgroup pool in v1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YTr0zvythCIJk4Xb@kroah.com>
Date:   Fri, 10 Sep 2021 08:01:50 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     "taoyi.ty" <escape@...ux.alibaba.com>
Cc:     tj@...nel.org, lizefan.x@...edance.com, hannes@...xchg.org,
        mcgrof@...nel.org, keescook@...omium.org, yzaikin@...gle.com,
        linux-kernel@...r.kernel.org, cgroups@...r.kernel.org,
        linux-fsdevel@...r.kernel.org, shanpeic@...ux.alibaba.com
Subject: Re: [RFC PATCH 0/2] support cgroup pool in v1

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