Messages in this thread | | | Date | Wed, 3 May 2023 14:56:44 -0400 | From | Kent Overstreet <> | Subject | Re: [PATCH 00/40] Memory allocation profiling |
| |
On Wed, May 03, 2023 at 08:40:07AM -1000, Tejun Heo wrote: > > Yeah, easy / default visibility argument does make sense to me. > > So, a bit of addition here. If this is the thrust, the debugfs part seems > rather redundant, right? That's trivially obtainable with tracing / bpf and > in a more flexible and performant manner. Also, are we happy with recording > just single depth for persistent tracking?
Not sure what you're envisioning?
I'd consider the debugfs interface pretty integral; it's much more discoverable for users, and it's hardly any code out of the whole patchset.
Single depth was discussed previously. It's what makes it cheap enough to be always-on (saving stack traces is expensive!), and I find the output much more usable than e.g. page owner.
| |