From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751771AbcCaAze (ORCPT ); Wed, 30 Mar 2016 20:55:34 -0400 Received: from LGEAMRELO13.lge.com ([156.147.23.53]:44853 "EHLO lgeamrelo13.lge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750905AbcCaAzc (ORCPT ); Wed, 30 Mar 2016 20:55:32 -0400 X-Original-SENDERIP: 156.147.1.126 X-Original-MAILFROM: minchan@kernel.org X-Original-SENDERIP: 10.177.223.161 X-Original-MAILFROM: minchan@kernel.org Date: Thu, 31 Mar 2016 09:57:17 +0900 From: Minchan Kim To: Andrew Morton Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, jlayton@poochiereds.net, bfields@fieldses.org, Vlastimil Babka , Joonsoo Kim , koct9i@gmail.com, aquini@redhat.com, virtualization@lists.linux-foundation.org, Mel Gorman , Hugh Dickins , Sergey Senozhatsky , Rik van Riel , rknize@motorola.com, Gioh Kim , Sangseok Lee , Chan Gyun Jeong , Al Viro , YiPing Xu Subject: Re: [PATCH v3 00/16] Support non-lru page migration Message-ID: <20160331005717.GB6736@bbox> References: <1459321935-3655-1-git-send-email-minchan@kernel.org> <20160330161141.4332b189e7a4930e117d765b@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160330161141.4332b189e7a4930e117d765b@linux-foundation.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 30, 2016 at 04:11:41PM -0700, Andrew Morton wrote: > On Wed, 30 Mar 2016 16:11:59 +0900 Minchan Kim wrote: > > > Recently, I got many reports about perfermance degradation > > in embedded system(Android mobile phone, webOS TV and so on) > > and failed to fork easily. > > > > The problem was fragmentation caused by zram and GPU driver > > pages. Their pages cannot be migrated so compaction cannot > > work well, either so reclaimer ends up shrinking all of working > > set pages. It made system very slow and even to fail to fork > > easily. > > > > Other pain point is that they cannot work with CMA. > > Most of CMA memory space could be idle(ie, it could be used > > for movable pages unless driver is using) but if driver(i.e., > > zram) cannot migrate his page, that memory space could be > > wasted. In our product which has big CMA memory, it reclaims > > zones too exccessively although there are lots of free space > > in CMA so system was very slow easily. > > > > To solve these problem, this patch try to add facility to > > migrate non-lru pages via introducing new friend functions > > of migratepage in address_space_operation and new page flags. > > > > (isolate_page, putback_page) > > (PG_movable, PG_isolated) > > > > For details, please read description in > > "mm/compaction: support non-lru movable page migration". > > OK, I grabbed all these. > > I wonder about testing coverage during the -next period. How many > people are likely to exercise these code paths in a serious way before > it all hits mainline? I asked this patchset to production team in my company for stress testing. They alaways catch zram/zsmalloc bugs I have missed so I hope they help me well, too. About ballooning part, I hope Rafael Aquini get a time to review and test it. Other than that, IOW, linux-next will have a enough time to test common migration part modification, I guess. :) Thanks.