Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp3874275ybi; Fri, 19 Jul 2019 10:31:56 -0700 (PDT) X-Google-Smtp-Source: APXvYqz7WgptpanuDbkVOJpePqvtBMGpAFe05hY58rxCCdbjLDHCYnk1DDs3Na4h5oEvdxUF6gk4 X-Received: by 2002:a63:4d05:: with SMTP id a5mr51600221pgb.19.1563557516221; Fri, 19 Jul 2019 10:31:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563557516; cv=none; d=google.com; s=arc-20160816; b=et/W99mXaTim2TJgeDrAbBaOpJDubmffIf0kWDGSbZ0kVtvccTw4Ih2gw35x4AVQ1S 39Fz/0gbuYq24RHQD8nLzqMNvWsdWzJilQHtcEH5opzR7IgbK8SsYz2pCIGzJLx1TVhs dQKyVX9DZd+hvlXi/bL0ty4Mwhrm8+JLTmprIeOi+iw9O2/bLHcJ6o+ySK+djfQuGARu SZQip10YrnrrC9LY30I+eIuzMilBNWTVzRnjxHgRCgEP9tK+i5CDkTNS8kwMKYY+u0DX I65zttRvkQrkfG9cOFJvVJWpA+AwXQdRVVRlf6yUGHrCRTzbawwxaf0GmiznykTlNCa4 BK4g== 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-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=oW57uqhu8/q+PMf+PtJdsWnbwVsxc8CylxUYzsEXDS4=; b=StmgabWHtMldFQs3WxVPO4ItMQKjKS+XbJ27kVc9E9mLVndGU2yn5h+lCHjwCdStSi hnvG1Olm8ADfcUuuBGI5xz19RzHporCxFEKh8z76BaZs0s0IOX+1S5bXOX/Vt69drSx7 TV1PtdCuy4Yv5Y2lcYY+3jqA7CuFEr+xLtOgHoAjmC+naXbRbI0C2jJkP107QqYOPzH7 adCUJAiuMsLrhssiDK/cejRovGJzYBc6NmcAApu4yp3pAzIS3BYKsf4PctZSrkBGPEnK aNgAQBpN7zrGFySH4SXsKR+l8aorq36bizDu9ClIgn02hgE9IV6NfTO0cmcy9o3qJzS2 G0Cw== 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 s14si2409480pgj.347.2019.07.19.10.31.41; Fri, 19 Jul 2019 10:31:56 -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 S1730177AbfGSQrP convert rfc822-to-8bit (ORCPT + 99 others); Fri, 19 Jul 2019 12:47:15 -0400 Received: from mx2.suse.de ([195.135.220.15]:43608 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727528AbfGSQrP (ORCPT ); Fri, 19 Jul 2019 12:47:15 -0400 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 80171AF9C; Fri, 19 Jul 2019 16:47:13 +0000 (UTC) Date: Fri, 19 Jul 2019 18:47:11 +0200 From: Michal =?iso-8859-1?Q?Koutn=FD?= To: =?utf-8?B?546L6LSH?= Cc: keescook@chromium.org, hannes@cmpxchg.org, vdavydov.dev@gmail.com, Peter Zijlstra , mcgrof@kernel.org, mhocko@kernel.org, linux-mm@kvack.org, Ingo Molnar , riel@surriel.com, Mel Gorman , cgroups@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/4] numa: introduce per-cgroup numa balancing locality, statistic Message-ID: <20190719164711.GB854@blackbody.suse.cz> References: <60b59306-5e36-e587-9145-e90657daec41@linux.alibaba.com> <3ac9b43a-cc80-01be-0079-df008a71ce4b@linux.alibaba.com> <20190711134754.GD3402@hirez.programming.kicks-ass.net> <20190712075815.GN3402@hirez.programming.kicks-ass.net> <37474414-1a54-8e3a-60df-eb7e5e1cc1ed@linux.alibaba.com> <20190712094214.GR3402@hirez.programming.kicks-ass.net> <20190715121025.GN9035@blackbody.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8BIT 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 Tue, Jul 16, 2019 at 10:41:36AM +0800, 王贇 wrote: > Actually whatever the memory node sets or cpu allow sets is, it will > take effect on task's behavior regarding memory location and cpu > location, while the locality only care about the results rather than > the sets. My previous response missed much of the context, so it was a bit off. I see what you mean by the locality now. Alas, I can't assess whether it's the right thing to do regarding NUMA behavior that you try to optimize (i.e. you need an answer from someone more familiar with NUMA balancing). Michal