Re: [PATCH 2/9] lib/ref_tracker: compact stacktraces before printing

[Eric Dumazet]

On Fri, Feb 18, 2022 at 2:55 AM Andrzej Hajda <andrzej.hajda@xxxxxxxxx> wrote:
>

> OK, could be faster and less invasive.
> Other solution would be keeping the array in dir and update in every
> tracker alloc/free, this way we avoid iteration over potentially big
> list, but it would cost memory and since printing is rather rare I am
> not sure if it is worth.

printing is extremely rare [1]

We want to use ref_tracker in production, we need to keep the fast
path as fast as possible ;)

[1] If you think about providing access to the traces from sysfs, we
might need to make sure we do not hold the dir spinlock
during the expensive generation of the output data.