Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp4133897imu; Mon, 12 Nov 2018 06:22:31 -0800 (PST) X-Google-Smtp-Source: AJdET5fiTycUrF5jtN6qSHNGPq0tda1tIKCryC2xZQ0q7gFhxgdMMQ2/VwOAsUP5pl9NIy6RvUqH X-Received: by 2002:a62:7dcc:: with SMTP id y195-v6mr1113718pfc.60.1542032551686; Mon, 12 Nov 2018 06:22:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542032551; cv=none; d=google.com; s=arc-20160816; b=gbE0b5LpBb9PPqSsmpnRKEmKwSWvMue2wULgYJBcKSXLBGiLTyxd2Qn1IOYxThknKB x0JwxTMR91Y0Pz+aRAx4pwUA4UPMjG4N79LN2OD9xyvuwHdSPld9RgpI/iB97uLCS2+k AtEVtQ1sRwyUs/zxDClmqjwBUprgNjQKS3Sou89dDp3AI1Z3hP2xv2jeLqVQKLeQxF26 f16M+yX12bj6I98sREWO57c2Uddu6VIXfEDoWrc5PSOokLZdcDCffiCgEupXjPiq8Rff P2LAifI1k9D7g2uK0ccGhJMxvD8pKd1wQhQ3oYhguA3U2l1ydVOyIDv/cG3lX1x+di3z 3Awg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=Eq9TALixN5SqVZmqEH2fPaodA6j5CrQhdHH7aVYVRpc=; b=JCe1gPAHUgkT4tB4WDsnf+MYBy+FBm/gGboULmsG0b3t3lKhP/KbeJC6EsALPeet6w xm+hGge4a6sMN77p+qFvWLs6SpSyVt+EidYTDX13Kthqp4ce8deKGpGcK7Y3SBISXoNv rSE2P42b0XzG0Tuc4mfLAnt9PdYIsOCq0m6n+qEfqpOOQenW/PZvmllakRXsyiiQMHLo 7leqGT1ifDk9wZlWFLcP5xzLOUxJAO0GRWniqeKUgDsDcNJPXACAzKh+Bq2yHKDQtUKr RqUltliRlD3wd79D3Mnkra8rctgXuOuJ9hDKzuq+QHqddUODjaCIKwFRFWdaddF+6SDD aUrw== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b65si16699698pgc.259.2018.11.12.06.22.15; Mon, 12 Nov 2018 06:22:31 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729943AbeKMAOr (ORCPT + 99 others); Mon, 12 Nov 2018 19:14:47 -0500 Received: from mga17.intel.com ([192.55.52.151]:21203 "EHLO mga17.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729380AbeKMAOr (ORCPT ); Mon, 12 Nov 2018 19:14:47 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Nov 2018 06:21:18 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,495,1534834800"; d="scan'208";a="85216844" Received: from avandeve-mobl.amr.corp.intel.com (HELO [10.254.49.202]) ([10.254.49.202]) by fmsmga007.fm.intel.com with ESMTP; 12 Nov 2018 06:21:18 -0800 Subject: Re: [RFC PATCH v1 2/2] proc: add /proc//thread_state To: Peter Zijlstra , Ingo Molnar Cc: Aubrey Li , tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, ak@linux.intel.com, tim.c.chen@linux.intel.com, linux-kernel@vger.kernel.org, Aubrey Li References: <1541528590-30296-1-git-send-email-aubrey.li@intel.com> <1541528590-30296-2-git-send-email-aubrey.li@intel.com> <20181108063246.GA13233@gmail.com> <20181108101729.GP9761@hirez.programming.kicks-ass.net> <20181112053147.GA78520@gmail.com> <20181112085650.GM3056@worktop> From: Arjan van de Ven Message-ID: Date: Mon, 12 Nov 2018 06:21:17 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20181112085650.GM3056@worktop> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >> I'd prefer the kernel to do such clustering... > > I think that is a next step. > > Also, while the kernel can do this at a best effort basis, it cannot > take into account things the kernel doesn't know about, like high > priority job peak load etc.., things a job scheduler would know. > > Then again, a job scheduler would likely already know about the AVX > state anyway. the job scheduler can guess. unless it can also *measure* it won't know for sure... so even in that scenario having a decent way to report actuals is useful >