RFC lock contention tracking slimmed down
Get series with b4
b4 am 1181165602.7133.18.camel@dixVersions newest first
- v1 RFC Latest4 patches 27 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | statistics: no include hell for usersinclude/ lib/ | +23 | 2 replies | |
| 2/4 | statistics: cleanupsdrivers/ include/ lib/ | +100 | 0 replies | |
| 3/4 | statistics: sets of statistics in single fileinclude/ lib/ | +315 | 0 replies | |
| 4/4 | lock contention tracking slimmed downinclude/ kernel/ kernel/ | +76 | 25 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC] [Patch 0/4] lock contention tracking slimmed down
We can save many lines of code in the lock contention tracking patches by using some common code which implements statistics in a generic way.
Data is still gathered per cpu; output goes to debugfs files. Several ideas that went into the lock contention tracking patches can be found in the statistics infrastructure as well.
Please see the last patch for details and for some sample output. The first three patches just prepare the statistics infrastructure for this new use case.
Feel free to pick at any rough edge you want me to smooth out, if you are interested in this approach.
[Patch 1/4] statistics: no include hell for users [Patch 2/4] statistics: cleanups
[Patch 3/4] statistics: sets of statistics in single file [Patch 4/4] lock contention tracking slimmed down
Please mind that the patches are against 2.6.22-rc3-mm1. They don't apply against 2.6.22-rc4-mm1. (The statistics library functions have been dropped, because a couple more users would be nice.)
Ah, and you might need to add CONFIG_STATISTICS to Kconfig of the architecture of your choice (see s390).