Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp6092421ybv; Tue, 18 Feb 2020 09:43:06 -0800 (PST) X-Google-Smtp-Source: APXvYqx3r494fl8VYUS6cnmY9FxNQoczgnGzfT1D5Ejl7vP3avDyx3Q3ZmQEAXWzf77Zp8cpLF1s X-Received: by 2002:a9d:68c8:: with SMTP id i8mr17152675oto.34.1582047786741; Tue, 18 Feb 2020 09:43:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582047786; cv=none; d=google.com; s=arc-20160816; b=SdGhqBy0TUssvJvVY/ICQTr9gDHhmVoKYaurgkP+96wCnVaQX1HhyP36atUmNpBbQW Gy1qnLlUyTfKXPb/mjLOlVo2mRoWmWZSRb9DhMWditxTWC7sxdqio2onPdHikPtC06pM Uqa8w7I6DDGv9RE3FbVi6SyzsXHXKRqAV3B+il3RYQdmqgYzv3DEo05HRzzA1kp4roFp ouNf/lCe745zfMXVXph9Hzvd42Gfp7xGgohyH+lYLqrr7KNbXA4R5z0PLjAKGcdQbd1n yvwIOj5KvNEASyRtFqBZReapl2lNwo86xoZ4irdSBwR+4lR4g691mvYQ8LPXB17FuZ9m +yqA== 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=EfkYH+pypdVfg5FWV9H1TX81vgB/9D9+PYGlLkUqr2k=; b=kNt1XpqUzvL/Ux7OIRK7jZy/IWzfbAnvJTfi7188chaH1J/iqECokcPukhDH7xB0Ec 47s4iphlIFOHjZtEsB1RN8FlwTxCuKAC3gwbsu8Gy27DnAHbG29SD6K/n3JZK8iwAq8N 3/kkh4TsuczdTSADPWqSmIBpLLlmWi7BM+0V7CSbpiJG7N51vqNlG8+I/moCQOpVhQLd bb+E6FrcqfOfX9lDqeUI+BjZxRWRyHL9SH58wXYQl9BDT4U9L830Q6JMcVNGB3CkCD0o TACE3GTWRz5cYtZCWBuoiqWRjZOORHESAXs7E8AWyt2nbvjGsaH4Hfr3oXHqe3Vjoz2f WtZg== 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 f190si8665079oig.229.2020.02.18.09.42.54; Tue, 18 Feb 2020 09:43:06 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726634AbgBRRlZ (ORCPT + 99 others); Tue, 18 Feb 2020 12:41:25 -0500 Received: from mx2.suse.de ([195.135.220.15]:34252 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726403AbgBRRlY (ORCPT ); Tue, 18 Feb 2020 12:41:24 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id AC980ADAA; Tue, 18 Feb 2020 17:41:22 +0000 (UTC) Date: Tue, 18 Feb 2020 17:41:19 +0000 From: Mel Gorman To: Valentin Schneider Cc: Vincent Guittot , mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com, dietmar.eggemann@arm.com, rostedt@goodmis.org, bsegall@google.com, linux-kernel@vger.kernel.org, pauld@redhat.com, parth@linux.ibm.com, hdanton@sina.com Subject: Re: [PATCH v2 2/5] sched/numa: Replace runnable_load_avg by load_avg Message-ID: <20200218174119.GG3420@suse.de> References: <20200214152729.6059-1-vincent.guittot@linaro.org> <20200214152729.6059-3-vincent.guittot@linaro.org> <20200218153801.GF3420@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 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 Tue, Feb 18, 2020 at 04:50:48PM +0000, Valentin Schneider wrote: > On 18/02/2020 15:38, Mel Gorman wrote: > >> > >> Could we reuse group_type instead? The definitions are the same modulo > >> s/group/node/. > >> > > > > I kept the naming because there is the remote possibility that NUMA > > balancing will deviate in some fashion. Right now, it's harmless. > > > > Since it's just a subset ATM I'd go for the reuse and change that later if > shown a split is required, but fair enough. > I would feel that I was churning code for the sake of it. > > I didn't merge that part of the first version of my series. I was > > waiting to see how the implementation for allowing a small degree of > > imbalance looks like. If it's entirely confined in adjust_numa_balance > ^^^^^^^^^^^^^^^^^^^ > Apologies if that's a newbie question, but I'm not familiar with that one. > Would that be added in your reconciliation series? I've only had a brief > look at it yet (it's next on the chopping block). > I should have wrote adjust_numa_imbalance but yes, it's part of the reconciled series so that NUMA balancing and the load balancer use the same helper. > > Yikes, no I'd rather not do that. Basically all I did before was create > > a common helper like __lb_has_capacity that only took basic types as > > parameters. group_has_capacity and numa_has_capacity were simple wrappers > > that read the correct fields from their respective stats structures. > > > > That's more sensible indeed. It'd definitely be nice to actually reconcile > the two balancers with these common helpers, though I guess it doesn't > *have* to happen with this very patch. Yep, it can happen at a later time. As it stands, I think the reconciled series stands on its own even though there are further improvements that could be built on top. -- Mel Gorman SUSE Labs