From: Arjan van de Ven <arjan@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@kernel.org>
Cc: Aubrey Li <aubrey.li@intel.com>,
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 <aubrey.li@linux.intel.com>
Subject: Re: [RFC PATCH v1 2/2] proc: add /proc/<pid>/thread_state
Date: Mon, 12 Nov 2018 06:21:17 -0800 [thread overview]
Message-ID: <d8a68174-70b0-8c6c-3293-b4ebb717d39e@linux.intel.com> (raw)
In-Reply-To: <20181112085650.GM3056@worktop>
>> 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
>
next prev parent reply other threads:[~2018-11-12 14:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 18:23 [RFC PATCH v1 1/2] x86/fpu: detect AVX task Aubrey Li
2018-11-06 18:23 ` [RFC PATCH v1 2/2] proc: add /proc/<pid>/thread_state Aubrey Li
2018-11-08 6:32 ` Ingo Molnar
2018-11-08 10:17 ` Peter Zijlstra
2018-11-08 14:03 ` Li, Aubrey
2018-11-12 5:31 ` Ingo Molnar
2018-11-12 7:53 ` Li, Aubrey
2018-11-12 8:56 ` Peter Zijlstra
2018-11-12 14:21 ` Arjan van de Ven [this message]
2018-11-07 17:41 ` [RFC PATCH v1 1/2] x86/fpu: detect AVX task Tim Chen
2018-11-08 0:31 ` Li, Aubrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d8a68174-70b0-8c6c-3293-b4ebb717d39e@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=ak@linux.intel.com \
--cc=aubrey.li@intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox