Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp5323819imm; Tue, 19 Jun 2018 08:36:52 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKbnyo1cY9BJwhx87qKEsMiXnnJOKiFDuD5fofxI6uZWxFLMaLVpulEbGrOvL5qSVvX0cZI X-Received: by 2002:a62:190d:: with SMTP id 13-v6mr18624503pfz.103.1529422612177; Tue, 19 Jun 2018 08:36:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529422612; cv=none; d=google.com; s=arc-20160816; b=UWYYf6qI5mUrMwF2ZAdWaF/m+rtPn643OAJekhFNK+lUpWTitdVf+Jb6pO751VYzNg 7JMXuNk0GE84f7aKGNGDp0eqTJZunDnqIm2/QriXdqf3Mv7aHMbEGandfs1x41O7zE6d 9oemkVDRBDXMiZ4rkY2aG8iudbl3EEw6VaZ/X0cQnIjJpSfHS331cKDLy6ycm8nISAwq 508L+lMDnA9Dmszht00NTA0w9zjoEwW7pNnSXfgp+HwZLSVifyTGEyv2ugXpUUDPFkI2 /XYp6LgGfq9hQLIPVWlUHBr44CLkIS8QkIr7G2SRuOO3c2pK7hY4RQbuvxNsWFFBZINE WymQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:message-id :in-reply-to:date:references:subject:cc:to:from :arc-authentication-results; bh=lCIAAaziwvZoE/hpCi1VSShjMKOiUPVDOQ8sVgop+RY=; b=acIpLplZUiWDo1KVOgP7z+UmwqxHKUMIQhprw+9P4PBHvuB08t+7L1FXesrKslca/K 9+SobMcogErzumnPBqhg3QU0677R+3PN06jVj/YmXmY5kEOFwCW0lafPApcVEcXge4YU mwnD1VEyGsOg+MIMikwK4lNh5yZMI7k5g8JAsWgfJ31npQVDLSBPWq054QRBR743xtE7 /pvYnujhB9YWJcDeBsFpu+XZJ89lxxQ3Ix7caOAW8APqOuNxvKtYO36KzbQoHYC0Y8/m 2WkG6NQPMeagczo/A/zefhzcJtAmEla+VJBzxYy4BivCOCS0vNAT1F/qwVoY6GmnVzD4 KUww== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g2-v6si14493021pgo.367.2018.06.19.08.36.38; Tue, 19 Jun 2018 08:36:52 -0700 (PDT) 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966719AbeFSPfo (ORCPT + 99 others); Tue, 19 Jun 2018 11:35:44 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:52582 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966516AbeFSPfn (ORCPT ); Tue, 19 Jun 2018 11:35:43 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id DA78F1596; Tue, 19 Jun 2018 08:35:42 -0700 (PDT) Received: from localhost (e105922-lin.cambridge.arm.com [10.1.206.33]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 7E43C3F557; Tue, 19 Jun 2018 08:35:42 -0700 (PDT) From: Punit Agrawal To: Michal Hocko Cc: Lorenzo Pieralisi , Xie XiuQi , Hanjun Guo , Bjorn Helgaas , , , Catalin Marinas , "Rafael J. Wysocki" , Will Deacon , Linux Kernel Mailing List , Jarkko Sakkinen , , , Greg Kroah-Hartman , Bjorn Helgaas , Andrew Morton , zhongjiang , linux-arm Subject: Re: [PATCH 1/2] arm64: avoid alloc memory on offline node References: <16c4db2f-bc70-d0f2-fb38-341d9117ff66@huawei.com> <20180611134303.GC75679@bhelgaas-glaptop.roam.corp.google.com> <20180611145330.GO13364@dhcp22.suse.cz> <87lgbk59gs.fsf@e105922-lin.cambridge.arm.com> <87bmce60y3.fsf@e105922-lin.cambridge.arm.com> <8b715082-14d4-f10b-d2d6-b23be7e4bf7e@huawei.com> <20180619120714.GE13685@dhcp22.suse.cz> <874lhz3pmn.fsf@e105922-lin.cambridge.arm.com> <20180619140818.GA16927@e107981-ln.cambridge.arm.com> <87wouu3jz1.fsf@e105922-lin.cambridge.arm.com> <20180619151425.GH13685@dhcp22.suse.cz> Date: Tue, 19 Jun 2018 16:35:40 +0100 In-Reply-To: <20180619151425.GH13685@dhcp22.suse.cz> (Michal Hocko's message of "Tue, 19 Jun 2018 17:14:25 +0200") Message-ID: <87r2l23i2b.fsf@e105922-lin.cambridge.arm.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Michal Hocko writes: > On Tue 19-06-18 15:54:26, Punit Agrawal wrote: > [...] >> In terms of $SUBJECT, I wonder if it's worth taking the original patch >> as a temporary fix (it'll also be easier to backport) while we work on >> fixing these other issues and enabling memoryless nodes. > > Well, x86 already does that but copying this antipatern is not really > nice. So it is good as a quick fix but it would be definitely much > better to have a robust fix. Who knows how many other places might hit > this. You certainly do not want to add a hack like this all over... Completely agree! I was only suggesting it as a temporary measure, especially as it looked like a proper fix might be invasive. Another fix might be to change the node specific allocation to node agnostic allocations. It isn't clear why the allocation is being requested from a specific node. I think Lorenzo suggested this in one of the threads. I've started putting together a set fixing the issues identified in this thread. It should give a better idea on the best course of action.