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]
Date:   Fri, 10 Sep 2021 10:11:53 +0800
From:   "taoyi.ty" <escape@...ux.alibaba.com>
To:     Greg KH <gregkh@...uxfoundation.org>
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 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.

thanks,

Yi Tao

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ