Re: [PATCH 2/3] weight for memcg background reclaim (Was Re: [PATCH V6 00/10] memcg: per cgroup background reclaim

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

 





On Thu, Apr 21, 2011 at 12:01 AM, KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> wrote:
On Wed, 20 Apr 2011 23:59:52 -0700
Ying Han <yinghan@xxxxxxxxxx> wrote:

> On Wed, Apr 20, 2011 at 11:38 PM, KAMEZAWA Hiroyuki <
> kamezawa.hiroyu@xxxxxxxxxxxxxx> wrote:
>
> > On Wed, 20 Apr 2011 23:11:42 -0700
> > Ying Han <yinghan@xxxxxxxxxx> wrote:
> >
> > > On Wed, Apr 20, 2011 at 8:48 PM, KAMEZAWA Hiroyuki <
> > > kamezawa.hiroyu@xxxxxxxxxxxxxx> wrote:

> n general, memcg-kswapd can reduce memory down to high watermak only when
> > the system is not busy. So, this logic tries to remove more memory from busy
> > cgroup to reduce 'hit limit'.
> >
>
> So, the "busy cgroup" here means the memcg has higher (usage - low)?
>

 high < usage < low < limit

Yes, if background reclaim wins, usage - high decreases.
If tasks on cgroup uses more memory than reclaim, usage - high increases even
if background reclaim runs. So, if usage-high is large, cgroup is busy.

Yes, I think I understand the (usage - high) in the calculation, but not the (low - high).

--Ying


Thanks,
-Kame



[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]