Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp4507418ybb; Tue, 14 Apr 2020 08:36:48 -0700 (PDT) X-Google-Smtp-Source: APiQypIJTPXpsdN5C0xEy+A5QVqLsLpEzP+vLySlngZCLCUj8r/LJtEvXYH3fuiNlX7RCQLvrzVM X-Received: by 2002:a17:907:20a2:: with SMTP id pw2mr719320ejb.252.1586878608209; Tue, 14 Apr 2020 08:36:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586878608; cv=none; d=google.com; s=arc-20160816; b=OMQXhrbc4PDYnEoF71H1PjdjyIcyyvxyIbaD4+HWpDQ3m7hsEMn/I9m+IQuYY+KJ8y LxS7fk6nDYr4WluZWzTxohZIUoxkkz1iynCYC7VVTKaCrhm9oB/ZKhc+T1MzNcu6zFvd wMtHWCfqZg5HibKYtKJfv6QsI2Okm+7FBzFQZsWBSiN8/YRHSlj1vnMcwNyNSNQ2ozWl ZRp71FdUI/0ppyip6i+fV5qIOK20EZUtgd1eP1UjkK0ILefZ5tOz2/kgLPOzuEcLU4tt vmq2+3af8mS6BKK5GEU5BLMv3aFS60pRBLQdKdQUroQVU8TbKH2H4VvdAFuH8yADRz50 CFmw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=uTBz1rbbgL6zk5oCQB/8KyAsL8UQNJVuo57K9Wkbz4A=; b=B0utmYg/SsNJpENuyeHnBkqVRWIJK2C/ij/fLEvapQpKE8PbK3pqoCcZPKRkdIaOZL 6l7z1CUg08fSLplHLPKxNDaf8OPAQjRwA6O5mpucXknWmfr/44iIWd3biKIdw/hhqxP2 IdBDQ4/l8u1mYD5zCj01VZK0sbmqtkTdC0/js/fvmWT3oI5YiplWFH3tRiY1hli/Qcwx G3VqNBKCMWhEoAmN3B4ozyhhcTvuxe+E314mACB0RAMtz0wk4qD4mrmvIAV2hMpzvvY6 W71mwk1EKq8oFKP7HSMARRa65ZDapf109OxjKvRd1+XnXZs3QEp28wQX5A0hzEZBAlwP 5MhQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=LzQG83K8; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y44si8502896ede.532.2020.04.14.08.36.24; Tue, 14 Apr 2020 08:36:48 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=LzQG83K8; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2502185AbgDNMpT (ORCPT + 99 others); Tue, 14 Apr 2020 08:45:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50330 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S2502239AbgDNMpJ (ORCPT ); Tue, 14 Apr 2020 08:45:09 -0400 Received: from mail-wr1-x444.google.com (mail-wr1-x444.google.com [IPv6:2a00:1450:4864:20::444]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F04DDC061A0C for ; Tue, 14 Apr 2020 05:45:08 -0700 (PDT) Received: by mail-wr1-x444.google.com with SMTP id k11so13536157wrp.5 for ; Tue, 14 Apr 2020 05:45:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=uTBz1rbbgL6zk5oCQB/8KyAsL8UQNJVuo57K9Wkbz4A=; b=LzQG83K8MK4ps2g8QyylKFIm0zrpVxZ0gGgLuWPGJNzanHJLR6yhAvZ3af7IPdx3iU Ist9HfBU/+k/yAfW72b4eSM5iw04G5QVw6ajNtZGE/m4JmTfSMEdGRLwlmyej9M+k/o+ kZQQJU8o1ugvCOocCHNWa+s73R667pZPNhWF3RNvkGe18BQLsCVDWey9wiMoNoU/bnpG kBiPnLJYOcrp2uHgXa0Fauxa7pJXA+afj8739cXgkktdzL2k41uOyE6lv85B4t/MsMrv 0q7XdUwn9y+pRc+Htso4Ob43Mfs0jbpg0fLZZL5xjYZ8kUiqz8U6RpXAa1wJwb4wAUkA pHmA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=uTBz1rbbgL6zk5oCQB/8KyAsL8UQNJVuo57K9Wkbz4A=; b=i7/Jl4WpIZt3EcukHhdxlHbgubgub0++iFGRiewHQzQzG+xABsdcLONRAiGjqASCrL x+BfB2TIBhG7b5r0/O8wM2icQ97DnQwnWqmTXMk0vL5GTFDqDysXbRzdxWKEeCqoxZpO Hj7OdOnqA8iWLr9575fs9CE5uHnHz4AmhDRG4CjKeMn96C6wzeLZ0VFVRv3G5uwteYua l490zuqO8tUNIUy1abZiXoTG+J+snRLCf+qzFT+NYeZh0gurM8ad/23kaF16s14RwFQ8 uvOHvZurZc65NSeFX0+luU9VJq2NtgCXSIHkfAxAqt4N344VhmUgNfdNFA4wbPFP14lY U31Q== X-Gm-Message-State: AGi0PubqmYEbEsl3qRAASDkpqoqJvKtMAFbw3FAHDg8/VNR7HgVpFTB0 8r3l3AQSOd5/7VcbkxXE7bGb/w== X-Received: by 2002:a5d:4843:: with SMTP id n3mr23406079wrs.7.1586868307403; Tue, 14 Apr 2020 05:45:07 -0700 (PDT) Received: from google.com ([2a00:79e0:d:110:d6cc:2030:37c1:9964]) by smtp.gmail.com with ESMTPSA id o9sm18957634wru.29.2020.04.14.05.45.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 14 Apr 2020 05:45:06 -0700 (PDT) Date: Tue, 14 Apr 2020 13:45:03 +0100 From: Quentin Perret To: Vincent Guittot Cc: Dietmar Eggemann , Ingo Molnar , Peter Zijlstra , Juri Lelli , Steven Rostedt , Luca Abeni , Daniel Bristot de Oliveira , Wei Wang , Alessio Balsini , Pavan Kondeti , Patrick Bellasi , Morten Rasmussen , Valentin Schneider , Qais Yousef , linux-kernel Subject: Re: [PATCH 1/4] sched/topology: Store root domain CPU capacity sum Message-ID: <20200414124503.GA236568@google.com> References: <20200408095012.3819-1-dietmar.eggemann@arm.com> <20200408095012.3819-2-dietmar.eggemann@arm.com> <42cc3878-4c57-96ba-3ebd-1b4d4ef87fae@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday 08 Apr 2020 at 19:03:57 (+0200), Vincent Guittot wrote: > Or we can do the opposite and only use capacity_orig_of()/rq->cpu_capacity_orig. > > Is there a case where the max cpu capacity changes over time ? So I > would prefer to use cpu_capacity_orig which is a field of scheduler > instead of always calling an external arch specific function Note however that using arch_scale_cpu_capacity() would be more efficient, especially on non-arm/arm64 systems where it is a compile-time constant. It's probably a matter of personal taste, but I find rq->cpu_capacity_orig superfluous. It wastes space without actually giving you anything no? Anybody remembers why it was introduced in the first place? Thanks, Quentin