From: Peter Zijlstra <peterz@infradead.org>
To: Peng Wang <rocking@linux.alibaba.com>
Cc: mingo@redhat.com, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
bristot@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add busy loop polling for idle SMT
Date: Fri, 19 Nov 2021 10:25:05 +0100 [thread overview]
Message-ID: <YZdtceRRxJQRt8cZ@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <e31e9b58-591b-c538-ccd1-5864e586ad02@linux.alibaba.com>
On Fri, Nov 19, 2021 at 11:19:03AM +0800, Peng Wang wrote:
>
> Yes, idle SMT busy loop polling can only provide approximately pipeline
> interference for normal instructions.
>
> When it comes to AVX works, we notice an idea modifing CPU time
> accounting[1], do you think the combination can lead to a feasible
> solution, or any other better ideas?
I'm not at all interested in solving this business model induced brain
trauma.
prev parent reply other threads:[~2021-11-19 9:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 11:51 [PATCH] Add busy loop polling for idle SMT Peng Wang
2021-11-16 11:51 ` [PATCH] sched/idle: support busy loop polling on idle SMT cpus Peng Wang
2021-11-16 23:08 ` kernel test robot
2021-11-18 11:36 ` kernel test robot
2021-11-27 15:50 ` kernel test robot
2021-11-17 10:58 ` [PATCH] Add busy loop polling for idle SMT Peter Zijlstra
2021-11-19 3:19 ` Peng Wang
2021-11-19 9:25 ` Peter Zijlstra [this message]
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=YZdtceRRxJQRt8cZ@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=rocking@linux.alibaba.com \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).