All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ying Han <yinghan@google.com>
To: Rik van Riel <riel@redhat.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Michal Hocko <mhocko@suse.cz>, Mel Gorman <mel@csn.ul.ie>,
	Hillf Danton <dhillf@gmail.com>, Hugh Dickins <hughd@google.com>,
	Dan Magenheimer <dan.magenheimer@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org
Subject: Re: [PATCH V3 0/2] memcg softlimit reclaim rework
Date: Fri, 20 Apr 2012 09:56:29 -0700	[thread overview]
Message-ID: <CALWz4iydcgDBPjV+49cesusbzZ2ePAk4WCHJmVSFS46VbwAq8A@mail.gmail.com> (raw)
In-Reply-To: <4F916FFE.2020401@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

On Fri, Apr 20, 2012 at 7:17 AM, Rik van Riel <riel@redhat.com> wrote:
> On 04/20/2012 04:21 AM, KAMEZAWA Hiroyuki wrote:
>
>> If you need smart victim selection under hierarchy, please implement
>> victim scheduler which choose A2 rather than A and A1. I think you
>> can do it.
>
>
> Ying and I spent a few hours working out exactly how to do
> this, a few weeks ago in San Francisco.
>
> She might still have the pictures of all the stuff we drew
> on the whiteboard.

Unfortunately,  I do have that on my phone. See the attachment if
those who might be interested.

Rik, Johannes and myself were discussing how to make the soft_limit
reclaim being smart on picking memcg, the same logic we currently use
to do get_scan_count() between file/anon lru.

After the ground work in this patch is done, I do plan to make that
happen. But for now, I like to focus on the ground work as starting
point.

--Ying


>
> --
> All rights reversed

[-- Attachment #2: soft_limit.JPG --]
[-- Type: image/jpeg, Size: 104741 bytes --]

  reply	other threads:[~2012-04-20 16:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17 16:37 [PATCH V3 0/2] memcg softlimit reclaim rework Ying Han
2012-04-18 12:24 ` Johannes Weiner
2012-04-18 18:00   ` Ying Han
2012-04-19 17:04     ` Michal Hocko
2012-04-19 17:47       ` Ying Han
2012-04-19 22:33         ` Johannes Weiner
2012-04-19 22:51           ` Johannes Weiner
2012-04-20  7:37           ` Ying Han
2012-04-20  8:21             ` KAMEZAWA Hiroyuki
2012-04-20 14:17               ` Rik van Riel
2012-04-20 16:56                 ` Ying Han [this message]
2012-04-20 13:17             ` Johannes Weiner
2012-04-20 17:44               ` Ying Han
2012-04-20 18:58                 ` Michal Hocko
2012-04-20 22:50                   ` Ying Han
2012-04-20 22:56                     ` Rik van Riel
2012-04-20 23:14                       ` Ying Han
2012-04-21  0:19                     ` Johannes Weiner
2012-04-21  0:48                       ` Johannes Weiner
2012-04-23 22:19                         ` Ying Han
2012-04-20 23:29                   ` Johannes Weiner
2012-04-23 13:59                     ` Michal Hocko
2012-04-20  8:28           ` Michal Hocko
2012-04-20  8:11         ` Michal Hocko
2012-04-20 17:22           ` Ying Han

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=CALWz4iydcgDBPjV+49cesusbzZ2ePAk4WCHJmVSFS46VbwAq8A@mail.gmail.com \
    --to=yinghan@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.magenheimer@oracle.com \
    --cc=dhillf@gmail.com \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=mhocko@suse.cz \
    --cc=riel@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.