From: Paul Mackerras <paulus@samba.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@redhat.com, hpa@zytor.com, eranian@google.com,
linux-kernel@vger.kernel.org, davem@davemloft.net,
fweisbec@gmail.com, ming.m.lin@intel.com, tglx@linutronix.de,
mingo@elte.hu, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] perf: Add group scheduling transactional APIs
Date: Mon, 10 May 2010 21:38:57 +1000 [thread overview]
Message-ID: <20100510113857.GA5131@brick.ozlabs.ibm.com> (raw)
In-Reply-To: <1273479115.5605.3329.camel@twins>
On Mon, May 10, 2010 at 10:11:55AM +0200, Peter Zijlstra wrote:
> Can't you compute n_txn_start by subtracting n_added from n_events ?
Well, n_added says how many have been added since hw_perf_disable, and
we could get multiple transactions inside a hw_perf_disable/enable
pair, if we're scheduling multiple groups on. So n_events - n_added
doesn't tell us how many have been added in this transaction -- unless
I'm mistaken and there is a one transaction per hw_perf_disable/enable
rule, but I didn't see that written anywhere, and it does seem to be
explicitly one transaction per group.
Paul.
next prev parent reply other threads:[~2010-05-10 11:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 5:56 [RFC][PATCH v2 1/4] perf: core, add " Lin Ming
2010-05-07 18:44 ` [tip:perf/core] perf: Add " tip-bot for Lin Ming
2010-05-07 21:55 ` Peter Zijlstra
2010-05-08 10:28 ` Paul Mackerras
2010-05-10 8:11 ` Peter Zijlstra
2010-05-10 11:38 ` Paul Mackerras [this message]
2010-05-11 15:43 ` [tip:perf/core] perf, powerpc: Implement " tip-bot for Lin Ming
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=20100510113857.GA5131@brick.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=davem@davemloft.net \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--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
Powered by JetHome