Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp7137600pxb; Thu, 18 Feb 2021 02:22:58 -0800 (PST) X-Google-Smtp-Source: ABdhPJwgrOK1uDXdXpyg96uJFYlTMhtjEqDB9YzrkLyo3wmRFq8AP800Fk29jx8cKAGYSJSpZEtY X-Received: by 2002:aa7:db01:: with SMTP id t1mr3443538eds.229.1613643778108; Thu, 18 Feb 2021 02:22:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1613643778; cv=none; d=google.com; s=arc-20160816; b=ENuoIGjYsmza5Q+MuRsjERm8BFZGnEllFtSnsifddLiLV4G8t3iAYruoJOm8IYMdpa s8j7U05Xuc9dziTabfEcm2VJ0uv6OHFFxgI22YhvR5TeBA7my2eUB/gmoZl5thWaXDeb ZJIbrseOurx+ZH2qqbFU54uN5Oa+zcaxd5xrasFDm5T17Qxsy+MzA6RvkRrRPcwAYpBz EeoMBUBcSupvc/D+Bs5OIr9u5P5eD/+QkbRovSP8P7lDIVv20IDerxd40MXO0Y7HniMU rzL6wpQK37Sl3G9wtQbFoe+mPEDAm28TyfKf+8UG6kajmlGZlYgl5Klgrx8KZJhXC/lq HhUw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=8RAszh7yrqFMBVVaDFUSTwmQ6Tv/ON0s4M9Tz9qKwYg=; b=UqAk9LvttzmCGuBSJYNsdjoMsV0jFheMyh9sYNks2GPpQZOMyA73sx139vsYN835zT gk+v3gIAUwGbTAOCktOgHlACffmaDFREBk0qp0S6R88HJp7hPqR1Y6amtCwTQiM1tjQs /Smcm1odVLzMenfj5AYwSGwW6J0pRrzkTrw/1kcLsXBMLH5ZYLiKhhm4MFBdkinQ4y19 kmVEqMuJtItNlrYXmX0u7Yu7zQo7uIvEPBVnJcNI/xHQJSTGkSQPJyHtG4j5KiLemvCB PV4VdZ/IAPimeQw2Pj8b5WJe1W2xx6O0NS83i7P4c+hrzNzK/1WdFJK01YNiKgcu8WdF Z90Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.com header.s=susede1 header.b=VeKsaAxM; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=suse.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id cb28si3474822edb.71.2021.02.18.02.22.33; Thu, 18 Feb 2021 02:22:58 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.com header.s=susede1 header.b=VeKsaAxM; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=suse.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232574AbhBRKKM (ORCPT + 99 others); Thu, 18 Feb 2021 05:10:12 -0500 Received: from mx2.suse.de ([195.135.220.15]:44214 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231261AbhBRI5F (ORCPT ); Thu, 18 Feb 2021 03:57:05 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1613638579; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=8RAszh7yrqFMBVVaDFUSTwmQ6Tv/ON0s4M9Tz9qKwYg=; b=VeKsaAxMxonW/fD/t12Ia80ScMOR6LGjZl7eGItzFNo4Yxu2+IDqnAMrfmw/FiXSEbHM3f HXfyeiLxxftUjGZRFMCg1ZCaP3LQ1lj+pif3w2fU6YWXwOLXZk9U1HHbsqhKLtpmujbkIK 1GzcAD728DMOsM6asbmcgSVMLoSjEzY= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 740FFAD87; Thu, 18 Feb 2021 08:56:19 +0000 (UTC) Date: Thu, 18 Feb 2021 09:56:18 +0100 From: Michal Hocko To: Minchan Kim Cc: Andrew Morton , linux-mm , LKML , david@redhat.com, joaodias@google.com Subject: Re: [PATCH] mm: be more verbose for alloc_contig_range faliures Message-ID: References: <20210217163603.429062-1-minchan@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210217163603.429062-1-minchan@kernel.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 17-02-21 08:36:03, Minchan Kim wrote: > alloc_contig_range is usually used on cma area or movable zone. > It's critical if the page migration fails on those areas so > dump more debugging message like memory_hotplug unless user > specifiy __GFP_NOWARN. I agree with David that this has a potential to generate a lot of output and it is not really clear whether it is worth it. Page isolation code already has REPORT_FAILURE mode which currently used only for the memory hotplug because this was just too noisy from the CMA path - d381c54760dc ("mm: only report isolation failures when offlining memory"). Maybe migration failures are less likely to fail but still. Doesn't CMA allocator provide some useful error reporting on its own? [...] > @@ -8736,8 +8747,11 @@ struct page *alloc_contig_pages(unsigned long nr_pages, gfp_t gfp_mask, > * and cause alloc_contig_range() to fail... > */ > spin_unlock_irqrestore(&zone->lock, flags); > + > + if (zone_idx(zone) != ZONE_MOVABLE) > + gfp_flags = gfp_mask | __GFP_NOWARN; Nack to this. Caller shouldn't tweak gfp mask of the caller. If we really want to control the reporting based on __GFP_NOWARN or a lack of it then this has to be under control of the caller. > ret = __alloc_contig_pages(pfn, nr_pages, > - gfp_mask); > + gfp_flags); > if (!ret) > return pfn_to_page(pfn); > spin_lock_irqsave(&zone->lock, flags); > -- > 2.30.0.478.g8a0d178c01-goog > -- Michal Hocko SUSE Labs