[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130617140108.GE5018@dhcp22.suse.cz>
Date: Mon, 17 Jun 2013 16:01:08 +0200
From: Michal Hocko <mhocko@...e.cz>
To: Andrew Morton <akpm@...ux-foundation.org>,
Johannes Weiner <hannes@...xchg.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc: linux-mm@...ck.org, cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org, Ying Han <yinghan@...gle.com>,
Hugh Dickins <hughd@...gle.com>,
Michel Lespinasse <walken@...gle.com>,
Greg Thelen <gthelen@...gle.com>, Tejun Heo <tj@...nel.org>,
Balbir Singh <bsingharora@...il.com>,
Glauber Costa <glommer@...il.com>
Subject: Re: [patch v4] Soft limit rework
On Tue 11-06-13 17:43:53, Michal Hocko wrote:
> JFYI, I have rebased the series on top of the current mmotm tree to
> catch up with Mel's changes in reclaim and other small things here and
> there. To be sure that the things are still good I have started my tests
> again which will take some time.
And it took way more time than I would like but the current mmotm is
broken and crashes/hangs and misbehaves in strange ways. At first I
thought it is my -mm git tree that is broken but then when I started
testing with linux-next I could see issues as well. I was able to reduce
the space to slab shrinkers rework but bisection led to nothing
reasonable. I will report those issues in a separate email when I
collect all necessary information.
In the meantime I will retest on top of my -mm tree without slab
shrinkers patches applied. This should be OK for the soft reclaim work
because memcg shrinkers are still not merged into mm tree and they
shouldn't be affected by the soft reclaim as the reclaim is per
shrink_zone now.
--
Michal Hocko
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists