From: Ying Han <yinghan@google.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Michal Hocko <mhocko@suse.cz>,
Balbir Singh <bsingharora@gmail.com>,
Rik van Riel <riel@redhat.com>, Hugh Dickins <hughd@google.com>,
Johannes Weiner <hannes@cmpxchg.org>, Mel Gorman <mel@csn.ul.ie>,
Pavel Emelyanov <xemul@openvz.org>,
linux-mm@kvack.org
Subject: Re: [PATCH] memcg: fix up documentation on global LRU.
Date: Mon, 6 Feb 2012 12:02:22 -0800 [thread overview]
Message-ID: <CALWz4izDB=ctQkuhqM_aSPo2M1kJ=PPFDjEY25EzRmKPF8vX+A@mail.gmail.com> (raw)
In-Reply-To: <20120206104856.e56680a2.kamezawa.hiroyu@jp.fujitsu.com>
On Sun, Feb 5, 2012 at 5:48 PM, KAMEZAWA Hiroyuki
<kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Fri, 3 Feb 2012 12:03:38 -0800
> Ying Han <yinghan@google.com> wrote:
>
>> On Thu, Feb 2, 2012 at 6:38 PM, KAMEZAWA Hiroyuki
>> <kamezawa.hiroyu@jp.fujitsu.com> wrote:
>> > On Thu, 2 Feb 2012 17:37:13 -0800
>> > Ying Han <yinghan@google.com> wrote:
>
>> >
>> > Do you want to do memory locking by setting swap_limit=0 ?
>>
>> hmm, not sure what do you mean here?
>>
>
> Do you want to add memory.swap.limit_in_bytes file for limitting swap
> and do memrory.swap.limit_in_bytes = 0
> for guaranteeing any anon pages will never be swapped-out ?
That's not what I was thinking. But I am quite curious what's our
decision making of not going there at the first place? I won't be
surprised to see objections of setting swap as separate limit, but
didn't find the pointer online yet.
Thanks
--Ying
>
>
>
> 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>
next prev parent reply other threads:[~2012-02-06 20:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 1:37 [PATCH] memcg: fix up documentation on global LRU Ying Han
2012-02-03 2:38 ` KAMEZAWA Hiroyuki
2012-02-03 20:03 ` Ying Han
2012-02-06 1:48 ` KAMEZAWA Hiroyuki
2012-02-06 20:02 ` Ying Han [this message]
2012-02-03 16:11 ` Michal Hocko
2012-02-03 20:15 ` Ying Han
2012-02-06 1:46 ` KAMEZAWA Hiroyuki
2012-02-06 20:00 ` Ying Han
2012-02-07 0:21 ` KAMEZAWA Hiroyuki
-- strict thread matches above, loose matches on Subject: below --
2012-02-06 20:19 Ying Han
2012-02-09 1:26 ` 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='CALWz4izDB=ctQkuhqM_aSPo2M1kJ=PPFDjEY25EzRmKPF8vX+A@mail.gmail.com' \
--to=yinghan@google.com \
--cc=bsingharora@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 \
--cc=xemul@openvz.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;
as well as URLs for NNTP newsgroup(s).