Re: [tip:perf/core] perf: Add group scheduling transactional APIs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:perf/core] perf: Add group scheduling transactional APIs
- From: Paul Mackerras <paulus@xxxxxxxxx>
- Date: Mon, 10 May 2010 21:38:57 +1000
- Cc: mingo@xxxxxxxxxx, hpa@xxxxxxxxx, eranian@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, davem@xxxxxxxxxxxxx, fweisbec@xxxxxxxxx, ming.m.lin@xxxxxxxxx, tglx@xxxxxxxxxxxxx, mingo@xxxxxxx, linux-tip-commits@xxxxxxxxxxxxxxx
- In-reply-to: <1273479115.5605.3329.camel@twins>
- References: <1272002160.5707.60.camel@xxxxxxxxxxxxxxxxxxx> <tip-6bde9b6ce0127e2a56228a2071536d422be31336@xxxxxxxxxxxxxx> <1273269355.1642.383.camel@laptop> <20100508102841.GA10650@xxxxxxxxxxxxxxxxxxxx> <1273479115.5605.3329.camel@twins>
- User-agent: Mutt/1.5.20 (2009-06-14)
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]