Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754212AbdHYAUG (ORCPT ); Thu, 24 Aug 2017 20:20:06 -0400 Received: from LGEAMRELO13.lge.com ([156.147.23.53]:41090 "EHLO lgeamrelo13.lge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753428AbdHYAUF (ORCPT ); Thu, 24 Aug 2017 20:20:05 -0400 X-Original-SENDERIP: 156.147.1.151 X-Original-MAILFROM: iamjoonsoo.kim@lge.com X-Original-SENDERIP: 10.177.222.138 X-Original-MAILFROM: iamjoonsoo.kim@lge.com Date: Fri, 25 Aug 2017 09:20:31 +0900 From: Joonsoo Kim To: Vlastimil Babka Cc: Andrew Morton , Michal Hocko , Mel Gorman , Johannes Weiner , "Aneesh Kumar K . V" , Minchan Kim , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE request Message-ID: <20170825002031.GD29701@js1304-P5Q-DELUXE> References: <1503553546-27450-1-git-send-email-iamjoonsoo.kim@lge.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Content-Length: 1770 Lines: 47 On Thu, Aug 24, 2017 at 11:41:58AM +0200, Vlastimil Babka wrote: > On 08/24/2017 07:45 AM, js1304@gmail.com wrote: > > From: Joonsoo Kim > > > > Freepage on ZONE_HIGHMEM doesn't work for kernel memory so it's not that > > important to reserve. When ZONE_MOVABLE is used, this problem would > > theorectically cause to decrease usable memory for GFP_HIGHUSER_MOVABLE > > allocation request which is mainly used for page cache and anon page > > allocation. So, fix it. > > > > And, defining sysctl_lowmem_reserve_ratio array by MAX_NR_ZONES - 1 size > > makes code complex. For example, if there is highmem system, following > > reserve ratio is activated for *NORMAL ZONE* which would be easyily > > misleading people. > > > > #ifdef CONFIG_HIGHMEM > > 32 > > #endif > > > > This patch also fix this situation by defining sysctl_lowmem_reserve_ratio > > array by MAX_NR_ZONES and place "#ifdef" to right place. > > > > Reviewed-by: Aneesh Kumar K.V > > Acked-by: Vlastimil Babka > > Looks like I did that almost year ago, so definitely had to refresh my > memory now :) > > Anyway now I looked more thoroughly and noticed that this change leaks > into the reported sysctl. On a 64bit system with ZONE_MOVABLE: > > before the patch: > vm.lowmem_reserve_ratio = 256 256 32 > > after the patch: > vm.lowmem_reserve_ratio = 256 256 32 2147483647 > > So if we indeed remove HIGHMEM from protection (c.f. Michal's mail), we > should do that differently than with the INT_MAX trick, IMHO. Hmm, this is already pointed by Minchan and I have answered that. lkml.kernel.org/r/<20170421013243.GA13966@js1304-desktop> If you have a better idea, please let me know. Thanks.