but if those things become useful to others, they should be "productized".But that's not the same thing as 'maintained with an unchanging interface for ever after'.
It might be a useful thing to see how many times the frobfs code calls frob_inode(). Essential, even, for performance tuning on large systems. But the frobfs developers want to have freedom to change their code to get rid of the frob_inode() call without breaking backwards compatibility. So there must be a way to label this stuff as usable in production, but not guaranteed to be there in future kernel versions.
In general any kind of instrumentation that works based on the kernel's internal data structures or control flow is useful to see but not a part of its API.
Copyright © 2018, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds