Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp4182173ybi; Mon, 15 Jul 2019 05:11:20 -0700 (PDT) X-Google-Smtp-Source: APXvYqwjbiY9blHCUms/VQL9/W35Wo7pw6kYtMz4H9lrxLG5m9TOaO93BuRCbaKHFXoLOtGNhzS6 X-Received: by 2002:a17:902:6ac6:: with SMTP id i6mr28218144plt.233.1563192679491; Mon, 15 Jul 2019 05:11:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563192679; cv=none; d=google.com; s=arc-20160816; b=h1s06x7xrJx3JLgTDpU9uX7MxWPw8Yd7xXVqgap/B/tj9XKDWNrn5K+4hhnCh71Nwc M5LCG+kjJ/TWiO371T+YNoRX9kLIvaQXDu7q66gkNNTRIwLDMDTd2jKjgK+U2EPLuS1u agxhyZ1lT+Jo54Oj0ZwJ45Aw2nyYeNFi2ZDnnYdplMz6Oy3H3zS4LM36e7oshCWXVr4u RqcHVgRuyJ+g3M8DKeOY7pFsn3F9nE4rZvqpFHSNLi1tP76e6Z/wyEwPaT57GTtljvhq N8P3qsHLBiIbso/+CWYsrgundpQ0MWL84I6S2mtyAAJMrQeQm/GDWDlkA1A9R4+vcW4w og+Q== 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=UuuNbPRY0c3mzJC92j4EJVmareBiHQSi5whjuhFbQA4=; b=y0rlLeG3EQWrzAYV2zs93s80ZxcsocBSJNZ7ZsK40Te0PC/REcv6LmdfT717h7NLN0 vKnrWTUDzWXIirz40JrPugNCvVrj6ARRx3v+YvBotjiBiRK/8SuBBenyc+7/k0bjWohg uEUiChIi/OSuBvhqRuBXDREkiL4Ps/YhC3ne8WjonPAfq72/K7iqLipw547AT1LzJuli N3+/CLV0/bMXY9MOf6Zyg/X+Bb+ec4aYgDB2svjt001HgVGejtFGuY+ggBQqJwIHSGvJ MvdAX7/z3Ys6BGBuZkDObZghIxVk/Ffz3+VwBlNsbX2nmDLfoib3YRkJEdYLlLxB6J1D qOHw== 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 f8si17078989pgi.191.2019.07.15.05.10.59; Mon, 15 Jul 2019 05:11:19 -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 S1729991AbfGOMKc (ORCPT + 99 others); Mon, 15 Jul 2019 08:10:32 -0400 Received: from mx2.suse.de ([195.135.220.15]:59806 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1729827AbfGOMKb (ORCPT ); Mon, 15 Jul 2019 08:10:31 -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 1D765AF0B; Mon, 15 Jul 2019 12:10:30 +0000 (UTC) Date: Mon, 15 Jul 2019 14:10:25 +0200 From: Michal =?iso-8859-1?Q?Koutn=FD?= To: =?utf-8?B?546L6LSH?= Cc: Peter Zijlstra , keescook@chromium.org, hannes@cmpxchg.org, vdavydov.dev@gmail.com, 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: <20190715121025.GN9035@blackbody.suse.cz> References: <209d247e-c1b2-3235-2722-dd7c1f896483@linux.alibaba.com> <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> 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 Hello Yun. On Fri, Jul 12, 2019 at 06:10:24PM +0800, 王贇 wrote: > Forgive me but I have no idea on how to combined this > with memory cgroup's locality hierarchical update... > parent memory cgroup do not have influence on mems_allowed > to it's children, correct? I'd recommend to look at the v2 of the cpuset controller that implements the hierarchical behavior among configured memory node sets. (My comment would better fit to [PATCH 3/4] numa: introduce numa group per task group IIUC, you could use cpuset controller to constraint memory nodes.) For the second part (accessing numa statistics, i.e. this patch), I wonder wheter this information wouldn't be better presented under the cpuset controller too. HTH, Michal