From: Alexey Budankov <alexey.budankov@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>, Song Liu <songliubraving@fb.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jolsa@redhat.com" <jolsa@redhat.com>,
Kernel Team <Kernel-team@fb.com>
Subject: Re: [RFC] perf: a different approach to perf_rotate_context()
Date: Mon, 5 Mar 2018 14:31:23 +0300 [thread overview]
Message-ID: <9ad03edb-7dc2-6fc8-7978-6257a7746aec@linux.intel.com> (raw)
In-Reply-To: <20180303174808.GJ25201@hirez.programming.kicks-ass.net>
On 03.03.2018 20:48, Peter Zijlstra wrote:
> On Sat, Mar 03, 2018 at 04:43:16PM +0000, Song Liu wrote:
>>> In any case, there's a ton of conflict against the patches here:
>>>
>>> https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git/log/?h=perf/testing
>>>
>>> And with those the idea was to move to a virtual time based scheduler
>>> (basically schedule those flexible events that have the biggest lag --
>>> that also solves 1).
>>
>> Thanks for these information. I will study this approach. Maybe that is
>> our path to PMU sharing.
>
> So I'm really not convinced on that whole PMU sharing.
>
>> What's is the status of this work? Would it
>> land in 4.17?
>
> These patches might make 4.17, they got held up because of the whole
> meltdown/spectre crap and I need to get back to them.
>
That work is long desired and would bring performance boost, specifically on
server systems in per-process profiling mode, accompanied by good speedup on
context switches. Undoubtedly meltdown/spectre related activity
substituted it at some point but that improvements would still bring
significant value and is still awaited.
BR,
Alexey
next prev parent reply other threads:[~2018-03-05 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 19:53 Song Liu
2018-03-03 13:39 ` Jiri Olsa
2018-03-03 16:16 ` Song Liu
2018-03-03 15:26 ` Peter Zijlstra
2018-03-03 16:43 ` Song Liu
2018-03-03 17:48 ` Peter Zijlstra
2018-03-05 11:31 ` Alexey Budankov [this message]
2018-03-13 0:39 ` Song Liu
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=9ad03edb-7dc2-6fc8-7978-6257a7746aec@linux.intel.com \
--to=alexey.budankov@linux.intel.com \
--cc=Kernel-team@fb.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.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
all inboxes | Powered by JetHome®