linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ying Han <yinghan@google.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org
Subject: Re: [LSF/MM TOPIC] [ATTEND] memcg: soft limit reclaim (continue) and others
Date: Wed, 1 Feb 2012 16:00:44 -0800	[thread overview]
Message-ID: <CALWz4iwHq6rX72gv4XMVAviqtFT8mjW2OgCBtjU6AVX94YsnGg@mail.gmail.com> (raw)
In-Reply-To: <20120201135442.0491d882.kamezawa.hiroyu@jp.fujitsu.com>

On Tue, Jan 31, 2012 at 8:54 PM, KAMEZAWA Hiroyuki
<kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Tue, 31 Jan 2012 11:59:40 -0800
> Ying Han <yinghan@google.com> wrote:
>
>> some topics that I would like to discuss this year:
>>
>> 1) we talked about soft limit redesign during last LSF, and there are
>> quite a lot of efforts and changes being pushed after that. I would
>> like to take this time to sync-up our efforts and also discuss some of
>> the remaining issues.
>>
>> Discussion from last year :
>> http://www.spinics.net/lists/linux-mm/msg17102.html and lots of
>> changes have been made since then.
>>
>
> Yes, it seems re-sync is required.
>
>> 2) memory.stat, this is the main stat file for all memcg statistics.
>> are we planning to keep stuff it for something like per-memcg
>> vmscan_stat, vmstat or not.
>>
>
> Could you calrify ? Do you want to have another stat file like memory.vmstat ?

I was planning to add per-memcg vmstat file at one point, but there
were discussions of just extending memory.stat. I don't mind to have
very long memory.stat file since my screen is now vertical anyway.
Just want to sync-up our final decision for later patches.

>
>
>> 3) root cgroup now becomes quite interesting, especially after we
>> bring back the exclusive lru to root. To be more specific, root cgroup
>> now is like a sink which contains pages allocated on its own, and also
>> pages being re-parented. Those pages won't be reclaimed until there is
>> a global pressure, and we want to see anything we can do better.
>>
>
> I'm sorry I can't get your point.
>
> Do you think it's better to shrink root mem cgroup LRU even if there are
> no memory pressure ?

The benefit will be reduced memory reclaim latency.

That is something I am thinking now. Now what we do in removing a
cgroup is re-parent all the pages, and root become a sink with all the
left-over pages. There is no external memory pressure to push those
pages out unless global reclaim, and the machine size will look
smaller and smaller on admin perspective.

I am thinking to use some existing reclaim mechanism to apply pressure
on those pages inside the kernel.

--Ying

> Or Do you think root memcg should have some soft limit and should be
> reclaimed in the same schedule line as other memcgs ? The benefit will be fairness.
>
> or other idea ?
>
> Thanks,
> -Kame
>

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  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@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2012-02-02  0:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31 19:59 Ying Han
2012-02-01  4:54 ` KAMEZAWA Hiroyuki
2012-02-02  0:00   ` Ying Han [this message]
2012-02-10  3:44     ` KAMEZAWA Hiroyuki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALWz4iwHq6rX72gv4XMVAviqtFT8mjW2OgCBtjU6AVX94YsnGg@mail.gmail.com \
    --to=yinghan@google.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox