On Wed, May 03, 2023 at 09:51:49AM +0200, Michal Hocko wrote: > Your answers have shown your insight into tracing is very limited. I > have a clear recollection there were many suggestions on how to get what > you need and willingness to help out. Repeating your previous position > will not help much to be honest with you. Please enlighten us, oh wise one. > > > - It has been brought up that this is duplicating functionality already > > > available via existing tracing infrastructure. You should make it very > > > clear why that is not suitable for the job > > > > Tracing people _claimed_ this, but never demonstrated it. > > The burden is on you and Suren. You are proposing the implement an > alternative tracing infrastructure. No, we're still waiting on the tracing people to _demonstrate_, not claim, that this is at all possible in a comparable way with tracing. It's not on us to make your argument for you, and before making accusations about honesty you should try to be more honest yourself. The expectations you're trying to level have never been the norm in the kernel community, sorry. When there's a technical argument about the best way to do something, _code wins_ and we've got working code to do something that hasn't been possible previously. There's absolutely no rule that "tracing has to be the one and only tool for kernel visibility". I'm considering the tracing discussion closed until someone in the pro-tracing camp shows something new. > > > - We already have page_owner infrastructure that provides allocation > > > tracking data. Why it cannot be used/extended? > > > > Page owner is also very high overhead, > > Is there any data to prove that claim? I would be really surprised that > page_owner would give higher overhead than page tagging with profiling > enabled (there is an allocation for each allocation request!!!). We can > discuss the bare bone page tagging comparision to page_owner because of > the full stack unwinding but is that overhead really prohibitively costly? > Can we reduce that by trimming the unwinder information? Honestly, this isn't terribly relevant, because as noted before page owner is limited to just page allocations. > > > and the output is not very user > > friendly (tracking full call stack means many related overhead gets > > split, not generally what you want), and it doesn't cover slab. > > Is this something we cannot do anything about? Have you explored any > potential ways? > > > This tracks _all_ memory allocations - slab, page, vmalloc, percpu. Michel, the discussions with you seem to perpetually go in circles; it's clear you're negative on the patchset, you keep raising the same objections while refusing to concede a single point. I believe I've answered enough, so I'll leave off further discussions with you.
