Hello! On Feb 10, 2014, at 9:40 PM, Al Viro wrote: > PS: I'm serious about the call graph, ideally along with the stack footprints > of all functions. At least it would give some idea how much do various > paths contribute... Of course, it's a real bitch to automate with the > amount of indirect calls you've got there - the tricky part is finding the > set of functions that might be called at given location ;-/ If you are really curious. Here are the three documents that used to be true soon after the functionality was first implemented. Since then a bunch of changes (sometimes passed as simplification, sometimes not) were done. But this is the best set of documentation available (other than the code, of course, which is, sadly, not super readable as you have noticed already). And it should give you some nightmares^Widea. The documents have sample callgraphs and state machines as initially envisioned (before meeting most of hard reality, should I add). http://wiki.lustre.org/images/1/1d/CLIO.pdf (meat starts at slide 6, statemachines at slide 11) http://wiki.lustre.org/images/6/66/CLIO-TOI.pdf (somewhat more in-depth version of the above). http://wiki.lustre.org/images/3/37/CLIO-TOI-notes.pdf - text only version with a lot of ascii flowcharts and lengthly explanations that was delivered to us when primary designer/developer of the code decided to leave our team. Bye, Oleg-- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
