From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-12.2 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 73659C4320A for ; Mon, 30 Aug 2021 12:27:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 571BA6054F for ; Mon, 30 Aug 2021 12:27:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231165AbhH3M1z (ORCPT ); Mon, 30 Aug 2021 08:27:55 -0400 Received: from smtp-out1.suse.de ([195.135.220.28]:47958 "EHLO smtp-out1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229673AbhH3M1s (ORCPT ); Mon, 30 Aug 2021 08:27:48 -0400 Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out1.suse.de (Postfix) with ESMTP id C365422125; Mon, 30 Aug 2021 12:26:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1630326413; 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=8GTpwtrUyWO9XgpVlTZOkCC2qFNxtbNrsk7UywRyxcY=; b=IiKxQxGSqSvsx87sUzydkrKMT2quQGaTHNUap9hixIkB5lGtPdLeXs48T+4OuBXquZZ9s2 9rAEOYC7vSLZdrP1WZHilueHAjBW7HXlMVie+Sqda4ExKnC4o2BJJW+iqbNOYfeOtxEiF5 9OomZg6un9qYoolKkA0zvT3mz++3ifc= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1630326413; 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=8GTpwtrUyWO9XgpVlTZOkCC2qFNxtbNrsk7UywRyxcY=; b=uCuEtT3WqENb+c1xZUhlPwRagSoYeaonm0vEiUmwBT2OBcBciYdC2MlagTO/ZgUjgwvHkV Z+9TquRtI2VBLtCw== Received: from suse.de (unknown [10.163.43.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by relay2.suse.de (Postfix) with ESMTPS id 3083CA3B8C; Mon, 30 Aug 2021 12:26:53 +0000 (UTC) Date: Mon, 30 Aug 2021 13:26:51 +0100 From: Mel Gorman To: Bharata B Rao Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, akpm@linux-foundation.org, kamezawa.hiroyu@jp.fujitsu.com, lee.schermerhorn@hp.com, Krupa.Ramakrishnan@amd.com, Sadagopan.Srinivasan@amd.com Subject: Re: [FIX PATCH 1/2] mm/page_alloc: Print node fallback order Message-ID: <20210830122651.GB4060@suse.de> References: <20210830121603.1081-1-bharata@amd.com> <20210830121603.1081-2-bharata@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <20210830121603.1081-2-bharata@amd.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 30, 2021 at 05:46:02PM +0530, Bharata B Rao wrote: > Print information message about the allocation fallback order > for each NUMA node during boot. > > No functional changes here. This makes it easier to illustrate > the problem in the node fallback list generation, which the > next patch fixes. > > Signed-off-by: Bharata B Rao While the message is just informational, I think it's possible that the bug could have been found earlier if this message was present so... Acked-by: Mel Gorman -- Mel Gorman SUSE Labs