linux-kernel - Re: [RFC PATCH 0/4] perf/core: Small event scheduling changes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091110051321.GE7897@elte.hu>
Date:	Tue, 10 Nov 2009 06:13:21 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Mike Galbraith <efault@....de>,
	Paul Mackerras <paulus@...ba.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC PATCH 0/4] perf/core: Small event scheduling changes


* Frederic Weisbecker <fweisbec@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/