From: Stijn Devriendt <highguy@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, efault@gmx.de, andrea@suse.de,
akpm@linux-foundation.org, Tejun Heo <tj@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC][PATCH] PERF_COUNT_SW_RUNNABLE_TASKS: measure and act upon parallellism
Date: Mon, 8 Feb 2010 12:52:15 +0100 [thread overview]
Message-ID: <c76f371a1002080352ta0a2f7jd7945dc8f834c2cd@mail.gmail.com> (raw)
In-Reply-To: <1265623245.1853.33.camel@laptop>
On Mon, Feb 8, 2010 at 11:00 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> On Sun, 2010-02-07 at 12:30 +0100, highguy@gmail.com wrote:
>
>> Here's an initial RFC patch for the parallallism
>> events for perf_events.
>
> OK, so you managed to rub me totally the wrong way with posting this
> yesterday:
> - you send me each patch twice
> - you used the horrible git sendmail default of --chain-reply-to
> (some day I'll write a script that will detect and auto-bounce
> series sent to me like that)
> - you failed to provide a changelog for any of the patches
> - some subjects were long enough to be a changelog
>
> Please don't do that again ;-)
Sorry for that. I'm still getting used to the thing called 'git'. Apart
from obviously sharing its name, there's not so
much we have in common so far... VCS experiences currently
don't go far beyond svn and the horrid CVS.
I just used the reply-list from the initial series about this subject,
perhaps you were listed twice in that one as well.
Isn't no longer making --chain-reply-to the default an option?
>
> Anyway, it did get me thinking, how about something like the below?
> <SNIP>
That pretty much looks like what I need at first sight. I'll definately
give it a very close look and test it out.
The perf_event approach would be nice, but the implementations
just seem to collide.
Thanks for taking the time anyway,
Stijn
next prev parent reply other threads:[~2010-02-08 11:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-07 11:30 highguy
2010-02-07 11:30 ` [PATCH 1/6] Move poll into perf_event and allow for wakeups when fd has not been mmap'd. This is useful when using read() to read out the current counter value highguy
2010-02-07 11:30 ` [PATCH 2/6] Allow min/max thresholds for wakeups highguy
2010-02-07 11:30 ` [PATCH 3/6] Add handlers for adding counter events, reading counter events, counter resets, wakeups. Renamed old read handler to update highguy
2010-02-07 11:30 ` [PATCH 4/6] Fix HW breakpoint handlers highguy
2010-02-07 11:30 ` [PATCH 5/6] Allow decrementing counters highguy
2010-02-07 11:30 ` [PATCH 6/6] Add PERF_COUNT_SW_RUNNABLE_TASKS highguy
2010-02-08 10:00 ` [RFC][PATCH] PERF_COUNT_SW_RUNNABLE_TASKS: measure and act upon parallellism Peter Zijlstra
2010-02-08 11:52 ` Stijn Devriendt [this message]
2010-02-08 11:59 ` Peter Zijlstra
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=c76f371a1002080352ta0a2f7jd7945dc8f834c2cd@mail.gmail.com \
--to=highguy@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrea@suse.de \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome