Re: [PATCH v3 0/6] perf script: Bounded and lazy symbol loading

[Alireza Haghdoost]

On Fri, Sep 25, 2026 at 2:56 PM Ian Rogers <irogers@xxxxxxxxxx> wrote:
>
> So, I'm pretty against the complexity of dealing with symbols that may
> fail due to a memory pressure issue.


Hi Ian,

That was aimed at --max-symbol-bytes. I'll drop it in v4.

Following the other thread [1], it looks like we agree that lazy loading is
worth having on its own. Whether or not the reference-counting series
lands, loading a name only when a sample needs it is a good change. As
in the numbers I posted there, it cuts memory use substantially and
makes perf script faster. I'll prepare v4 of this series without the
cap:

1. the ELF_C_READ_MMAP fix
2. reading DSO data from the debug file the symbol table came from
3. the shared duplicate-symbol selection
4. --lazy-load-symbols
5. the lazy-loading tests

Patches 2 and 3 stay because lazy loading needs them, and Namhyung
asked for them.

Namhyung, on that thread you suggested a limit that prints an offset
when the name is not loaded. I said I could do that for the byte cap
in v4. I'd rather land lazy loading first and add that limit later if
there is a need or interest.

[1] https://lore.kernel.org/all/20260928075237.3055101-1-irogers@xxxxxxxxxx/

Thanks,
Alireza