mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org, vince@deater.net,
	eranian@google.com, Arnaldo Carvalho de Melo <acme@infradead.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: [PATCH 0/2] perf: Scheduling optimizations
Date: Thu, 19 Jan 2017 18:43:28 +0200	[thread overview]
Message-ID: <20170119164330.22887-1-alexander.shishkin@linux.intel.com> (raw)

Hi Peter,

These here two patches deal with rescheduling on active contexts. The common
idea is that we shouldn't reschedule groups of higher priority than the ones
that are being added or scheduled in. 1/1 takes on the scheduling path, where
we don't want to touch cpu flexible groups if the scheduling context doesn't
carry pinned groups. 1/2 deals with the enable/install cases, where we have
to consider all four types of groups.

Alexander Shishkin (2):
  perf: Don't re-schedule cpu flexible events needlessly
  perf: Optimize event rescheduling on active contexts

 kernel/events/core.c | 86 ++++++++++++++++++++++++++++++++++++++++++++--------
 1 file changed, 74 insertions(+), 12 deletions(-)

-- 
2.11.0

             reply	other threads:[~2017-01-19 16:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19 16:43 Alexander Shishkin [this message]
2017-01-19 16:43 ` [PATCH 1/2] perf: Don't re-schedule cpu flexible events needlessly Alexander Shishkin
2017-01-30 11:58   ` [tip:perf/core] perf/core: Don't re-schedule CPU " tip-bot for Alexander Shishkin
2017-01-19 16:43 ` [PATCH 2/2] perf: Optimize event rescheduling on active contexts Alexander Shishkin
2017-01-30 11:59   ` [tip:perf/core] perf/core: " tip-bot for Alexander Shishkin

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=20170119164330.22887-1-alexander.shishkin@linux.intel.com \
    --to=alexander.shishkin@linux.intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@infradead.org \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=vince@deater.net \
    /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

Powered by JetHome