Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp10618444imu; Thu, 6 Dec 2018 04:12:49 -0800 (PST) X-Google-Smtp-Source: AFSGD/UMwiGE5EvjRU4yIAcKPv4LqglBTbeVJHy2NTLHlGs8SoHie2FmlN767brp1bUdibV4L9Ri X-Received: by 2002:a17:902:ba8b:: with SMTP id k11mr27791779pls.177.1544098369869; Thu, 06 Dec 2018 04:12:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544098369; cv=none; d=google.com; s=arc-20160816; b=RQsDNWgR3XXH9If3VkZgc2sx62TTtifS2ui77kzRwy9KWuFFAqMMkjkxe9tY+On6/e g6DT5CUJkDWv7nZYmnS/LbwSGUTZDmmauVS6eyY7uejitzcDe+Wpl1LGsoou5hLJt3NW UXy4S+A2oM85yCpp+P6QN7C+n56k+2Ew79hZofnu2KS2dPT8yuNo3B30vRs15W7jSkEW c5KCpJiM5nbdUaGNICkdad3hSRRz1kLb1PZovQM5RtgN6FFjvAr0OnLW8OcvoCBb5f08 cTSqvSfwwJd4xEo2NOi+Zyx0UrHEHwJMNiV68rdn2XnUxYvfFScVBsWsdSQagg2qaB/C DZNg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=xkXmymlqVIZcHrXPXCqB4zsPEF2edLPoYWxS33+ZjnM=; b=NWcXvI8El29YGWvEi+/Gxq7v0HyZAQcAlqque5AsreyJUYk1LyyatH975nzDniLT6j zNCahm9+C+5taoRwBFkzJTbLKit7I3sBWj6plVVguYdWvhIMisnBNzC6B41sk+2o4MkQ eZnjE1c+KjpY+Wc7Voe0SbJB13z0T2Vf0arb+Vgc3/giWcwNBQWL4QhxpybZQo+YxH5Y vIhkTkS5n6TxpthLsmO20YsnfmX4H419dJv169VtQ1vE4++qZ6nc8t1fl0NWuid53P9u IqENb8ug/SN+Et0PUjivjkjRvovyGyxWoxfnyJTla3azgPLv1dOmUYETzSA4wqJyI+02 AqpA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 87si143371pfs.7.2018.12.06.04.12.33; Thu, 06 Dec 2018 04:12:49 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729038AbeLFMLz (ORCPT + 99 others); Thu, 6 Dec 2018 07:11:55 -0500 Received: from mx2.suse.de ([195.135.220.15]:60914 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727763AbeLFMLz (ORCPT ); Thu, 6 Dec 2018 07:11:55 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 57A99AF63; Thu, 6 Dec 2018 12:11:53 +0000 (UTC) Date: Thu, 6 Dec 2018 13:11:52 +0100 From: Michal Hocko To: Pingfan Liu Cc: Vlastimil Babka , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andrew Morton , Mike Rapoport , Bjorn Helgaas , Jonathan Cameron Subject: Re: [PATCH] mm/alloc: fallback to first node if the wanted node offline Message-ID: <20181206121152.GH1286@dhcp22.suse.cz> References: <20181204085601.GC1286@dhcp22.suse.cz> <20181205092148.GA1286@dhcp22.suse.cz> <186b1804-3b1e-340e-f73b-f3c7e69649f5@suse.cz> <20181206082806.GB1286@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 06-12-18 18:44:03, Pingfan Liu wrote: > On Thu, Dec 6, 2018 at 6:03 PM Pingfan Liu wrote: [...] > > Which commit is this patch applied on? I can not apply it on latest linux tree. > > > I applied it by manual, will see the test result. I think it should > work since you instance all the node. > But there are two things worth to consider: > -1st. why x86 do not bring up all nodes by default, apparently it will > be more simple by that way What do you mean? Why it didn't bring up before? Or do you see some nodes not being brought up after this patch? > -2nd. there are other archs, do they obey the rules? I am afraid that each arch does its own initialization. -- Michal Hocko SUSE Labs