From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Mike Galbraith <efault@gmx.de>, Paul Mackerras <paulus@samba.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC PATCH 0/4] perf/core: Small event scheduling changes
Date: Tue, 10 Nov 2009 06:13:21 +0100 [thread overview]
Message-ID: <20091110051321.GE7897@elte.hu> (raw)
In-Reply-To: <1257711206-12243-1-git-send-email-fweisbec@gmail.com>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> Hi,
>
> This is an rfc patchset, only compile tested just to ensure I'm taking
> a good direction before going ahead.
>
> This is intended to rework a bit the perf event scheduling to
> guarantee a real priority of the pinned events over the volatile ones.
> This patchset handles such priority on task tick time only. But if the
> idea is agreed, I could expand that to every task event sched-in calls
> to guarantee the priority in every event rescheduling time.
>
> Thanks.
>
> Frederic Weisbecker (4):
> perf/core: split context's event group list into pinned and
> non-pinned lists
> perf/core: Optimize a bit rotate_ctx()
> perf/core: Split up pinned and non pinned processing
> perf/core: Schedule every pinned events before the the non-pinned
>
> include/linux/perf_event.h | 3 +-
> kernel/perf_event.c | 283 ++++++++++++++++++++++++++++++++-----------
> 2 files changed, 212 insertions(+), 74 deletions(-)
Sans the small naming suggestions i had, the general principle looks
good to me - it's a nice restructuring of the various scheduling rules
we have for events.
Ingo
next prev parent reply other threads:[~2009-11-10 5:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 20:13 [RFC PATCH 0/4] perf/core: Small event scheduling changes Frederic Weisbecker
2009-11-08 20:13 ` [RFC PATCH 1/4] perf/core: split context's event group list into pinned and non-pinned lists Frederic Weisbecker
2009-11-08 20:13 ` [RFC PATCH 2/4] perf/core: Optimize a bit rotate_ctx() Frederic Weisbecker
2009-11-08 20:13 ` [RFC PATCH 3/4] perf/core: Split up pinned and non pinned processing Frederic Weisbecker
2009-11-10 5:11 ` Ingo Molnar
2009-11-10 9:32 ` Frederic Weisbecker
2009-11-08 20:13 ` [RFC PATCH 4/4] perf/core: Schedule every pinned events before the the non-pinned Frederic Weisbecker
2009-11-10 10:10 ` Peter Zijlstra
2009-11-10 10:34 ` Frederic Weisbecker
2009-11-10 5:13 ` Ingo Molnar [this message]
2009-11-10 9:41 ` [RFC PATCH 0/4] perf/core: Small event scheduling changes Frederic Weisbecker
2009-11-10 9:47 ` Frederic Weisbecker
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=20091110051321.GE7897@elte.hu \
--to=mingo@elte.hu \
--cc=acme@redhat.com \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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