Re: [PATCH V2 3/5] memcg: set soft_limit_in_bytes to 0 by default

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Apr 11, 2012 at 5:45 PM, Rik van Riel <riel@xxxxxxxxxx> wrote:
> On 04/11/2012 06:00 PM, Ying Han wrote:
>>
>> 1. If soft_limit are all set to MAX, it wastes first three periority
>> iterations
>> without scanning anything.
>>
>> 2. By default every memcg is eligibal for softlimit reclaim, and we can
>> also
>> set the value to MAX for special memcg which is immune to soft limit
>> reclaim.
>>
>> This idea is based on discussion with Michal and Johannes from LSF.
>
>
> Combined with patch 2/5, would this not result in always
> returning "reclaim from this memcg" for groups without a
> configured softlimit, while groups with a configured
> softlimit only get reclaimed from when they are over
> their limit?

> Is that the desired behaviour when a system has some
> cgroups with a configured softlimit, and some without?

That is expected behavior. Basically after this change, by default all
memcgs are eligible for reclaim under global memory pressure. Only
those memcgs who sets their softlimit will be skipped if usage less
than softlimit.

Does it answer your question? I might misunderstood.

--Ying
> --
> All rights reversed

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]