On Fri, 18 Jan 2008 17:26:09 -0500 fche@redhat.com (Frank Ch. Eigler) wrote:sure. Every instrumentation you see is of the nested kind (since the lowest level of nesting is already automatic via wchan). If markers can provide me the following semantics, I'd be MORE than happy to use markers: If the code path is like this set_latency_reason("Reading file"); .... .... set_latency_reason("Allocating memory"); kmalloc() <--- blocks for 100 msec restore_latency_reason() .... restore_latency_reason(); via several layers of functions, the requirement is that the 100 msec is accounted to "reading file" and not "Allocating memory". But if some other codepath hits the allocating memory function, without an outer "set_latency_reason", it should be accounted to "Allocating memory". If markers can provide that semantics ... you sold me. -- If you want to reach me at my work email, use arjan@linux.intel.com For development, discussion and tips for power savings, visit http://www.lesswatts.org --
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
| Kok, Auke | Re: Linux 2.6.21-rc1 |
| Greg KH | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Jeff Garzik | Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver opt-in |
git: | |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Eric Dumazet | [PATCH] net: remove superfluous call to synchronize_net() |
