From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [PATCH v10 00/35] kmemcg shrinkers Date: Thu, 6 Jun 2013 00:47:27 -0700 Message-ID: <20130606004727.c28d62e9.akpm@linux-foundation.org> References: <1370287804-3481-1-git-send-email-glommer@openvz.org> <20130605160721.da995af82eb247ccf8f8537f@linux-foundation.org> <51B02347.60809@parallels.com> <20130606001855.48d9da2e.akpm@linux-foundation.org> <51B03C1F.4000501@parallels.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Glauber Costa , , Mel Gorman , Dave Chinner , , , , Michal Hocko , Johannes Weiner , , Greg Thelen To: Glauber Costa Return-path: In-Reply-To: <51B03C1F.4000501@parallels.com> Sender: owner-linux-mm@kvack.org List-Id: linux-fsdevel.vger.kernel.org On Thu, 6 Jun 2013 11:37:03 +0400 Glauber Costa wrote: > On 06/06/2013 11:18 AM, Andrew Morton wrote: > > The shrinker stuff seems sensible and straightforward and I expect we > > can proceed with that at the normal pace. The memcg changes struck me > > as being hairy as hell and I'd really like to see the other memcg > > people go through it carefully. > > > > Of course, "new series" doesn't give you an easily accessible tree to > > target. I could drop it all again to give you a clean shot at > > tomorrow's -next? > If you just keep them on top (not really sure how hard it is for you), I > can just remove them all and apply a new series on top. I could do that but then anyone else who wants to test the code has to do the same thing. Dropping them out of -next does seem the clean approach. We still need to work out what to do with memcg-debugging-facility-to-access-dangling-memcgs.patch btw. See other email. -- 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/ . Don't email: email@kvack.org