From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f71.google.com (mail-pa0-f71.google.com [209.85.220.71]) by kanga.kvack.org (Postfix) with ESMTP id 9DF116B0005 for ; Tue, 19 Jul 2016 02:39:58 -0400 (EDT) Received: by mail-pa0-f71.google.com with SMTP id q2so16772521pap.1 for ; Mon, 18 Jul 2016 23:39:58 -0700 (PDT) Received: from lgeamrelo11.lge.com (LGEAMRELO11.lge.com. [156.147.23.51]) by mx.google.com with ESMTP id 66si7778186pfe.135.2016.07.18.23.39.56 for ; Mon, 18 Jul 2016 23:39:57 -0700 (PDT) Date: Tue, 19 Jul 2016 15:44:06 +0900 From: Joonsoo Kim Subject: Re: [PATCH v3 09/17] mm, compaction: make whole_zone flag ignore cached scanner positions Message-ID: <20160719064406.GB17479@js1304-P5Q-DELUXE> References: <20160624095437.16385-1-vbabka@suse.cz> <20160624095437.16385-10-vbabka@suse.cz> <20160706050939.GD23627@js1304-P5Q-DELUXE> <1c0e2da2-115e-d676-cfec-e572270789ca@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1c0e2da2-115e-d676-cfec-e572270789ca@suse.cz> Sender: owner-linux-mm@kvack.org List-ID: To: Vlastimil Babka Cc: Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Michal Hocko , Mel Gorman , David Rientjes , Rik van Riel On Mon, Jul 18, 2016 at 11:12:51AM +0200, Vlastimil Babka wrote: > On 07/06/2016 07:09 AM, Joonsoo Kim wrote: > >On Fri, Jun 24, 2016 at 11:54:29AM +0200, Vlastimil Babka wrote: > >>A recent patch has added whole_zone flag that compaction sets when scanning > >>starts from the zone boundary, in order to report that zone has been fully > >>scanned in one attempt. For allocations that want to try really hard or cannot > >>fail, we will want to introduce a mode where scanning whole zone is guaranteed > >>regardless of the cached positions. > >> > >>This patch reuses the whole_zone flag in a way that if it's already passed true > >>to compaction, the cached scanner positions are ignored. Employing this flag > > > >Okay. But, please don't reset cached scanner position even if whole_zone > >flag is set. Just set cc->migrate_pfn and free_pfn, appropriately. With > > Won't that result in confusion on cached position updates during > compaction where it checks the previous cached position? I wonder > what kinds of corner cases it can bring... whole_zone would come along with ignore_skip_hint so I think that there is no problem on cached position updating. > > >your following patches, whole_zone could be set without any compaction > >try > > I don't understand what you mean here? Even after whole series, > whole_zone is only checked, and positions thus reset, after passing > the compaction_suitable() call from compact_zone(). So at that point > we can say that compaction is being actually tried and it's not a > drive-by reset? My point is that we should not initialize zone's cached pfn in case of the whole_zone because what compaction with COMPACT_PRIO_SYNC_FULL want is just to scan whole range. zone's cached pfn exists for efficiency and there is no reason to initialize it by compaction with COMPACT_PRIO_SYNC_FULL. If there are some parallel compaction users, they could be benefit from un-initialized zone's cached pfn so I'd like to leave them. Thanks. -- 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