Hello, Li.
On Mon, Mar 09, 2015 at 09:49:45AM +0800, Zefan Li wrote:
> Seems we are going to accept this feature. Is it because kmemcg won't be able
> to fullfill this requirement? And that's because kmemcg can only and will only
Yeah, pretty much.
> be able to control global kernel memory usage
Hi Tejun,
On 2015/3/2 23:22, Tejun Heo wrote:
> Hello,
>
> On Fri, Feb 27, 2015 at 03:17:19PM +1100, Aleksa Sarai wrote:
>> +config CGROUP_NPROC
>> +bool "Process number limiting on cgroups"
>> +depends on PAGE_COUNTER
>> +help
>> + This options enables the setting of process num
Hello,
On Fri, Feb 27, 2015 at 03:17:19PM +1100, Aleksa Sarai wrote:
> +config CGROUP_NPROC
> + bool "Process number limiting on cgroups"
> + depends on PAGE_COUNTER
> + help
> + This options enables the setting of process number limits in the scope
> + of a cgroup. Any att
Adds a new single-purpose nproc subsystem to limit the number of
tasks that can run inside a cgroup. Essentially this is an
implementation of RLIMIT_NPROC that will applies to a cgroup rather than
a process tree.
This is a step to being able to limit the global impact of a fork bomb
inside a cgrou
4 matches
Mail list logo