From: Hillf Danton <dhillf@gmail.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: linux-mm@kvack.org, Johannes Weiner <hannes@cmpxchg.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: memcg: remove checking reclaim order in soft limit reclaim
Date: Wed, 18 Jan 2012 20:30:41 +0800 [thread overview]
Message-ID: <CAJd=RBAyqPwKERQL4JyCO38gjE=y8_qasHTbLtMGWqtZ1JFnUg@mail.gmail.com> (raw)
In-Reply-To: <20120117140712.GC14907@tiehlicka.suse.cz>
On Tue, Jan 17, 2012 at 10:07 PM, Michal Hocko <mhocko@suse.cz> wrote:
> On Tue 17-01-12 21:29:52, Hillf Danton wrote:
>> On Tue, Jan 17, 2012 at 9:16 PM, Michal Hocko <mhocko@suse.cz> wrote:
>> > Hi,
>> >
>> > On Tue 17-01-12 20:47:59, Hillf Danton wrote:
>> >> If async order-O reclaim expected here, it is settled down when setting up scan
>> >> control, with scan priority hacked to be zero. Other than that, deny of reclaim
>> >> should be removed.
>> >
>> > Maybe I have misunderstood you but this is not right. The check is to
>> > protect from the _global_ reclaim with order > 0 when we prevent from
>> > memcg soft reclaim.
>> >
>> need to bear mm hog in this way?
>
> Could you be more specific? Are you trying to fix any particular
> problem?
>
My thought is simple, the outcome of softlimit reclaim depends little on the
value of reclaim order, zero or not, and only exceeding is reclaimed, so
selective response to swapd's request is incorrect.
> Global reclaim should take are of the global memory pressure. Soft
> reclaim is intended just to make its job easier. Btw. softlimit reclaim
> is on its way out of the kernel but this will not happen in 3.3.
>
I will check it in 3.3 if too late for 3.2.
Thanks
Hillf
--
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-01-18 12:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 12:47 Hillf Danton
2012-01-17 13:16 ` Michal Hocko
2012-01-17 13:29 ` Hillf Danton
2012-01-17 14:07 ` Michal Hocko
2012-01-18 12:30 ` Hillf Danton [this message]
2012-01-18 13:40 ` Michal Hocko
2012-01-18 14:01 ` Hillf Danton
2012-01-18 15:13 ` Michal Hocko
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='CAJd=RBAyqPwKERQL4JyCO38gjE=y8_qasHTbLtMGWqtZ1JFnUg@mail.gmail.com' \
--to=dhillf@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
/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