Dropping eBPF CPU Cost by About 90% with Memoization (Not AI Gen)

Very confused by the article. Is memoization new to the eBPF world? Did the author only just learn about it and wanted to use it?

In reality, the article is about correctly caching a path:policy mapping while working within the limitations of eBPF and Linux filesystem semantics. If you read the article in that context rather than wondering 'what is new and interesting about memoization in eBPF?' it's a lot more interesting.

I probably would have titled this 'Calculating cache keys for filesystem paths in eBPF' or something, since that's the cool and interesting problem that was solved.

So you highlight "Not AI Gen" but you call the solution "Agent"? :D

Umm, wouldn't this break if you moved a directory that is somewhere up the path? Seems like a security issue if you cache what policy applies but the policy could change by user action.

[dead]

I don't know what any of these acronyms mean. With just a little more explanation the article could be accessible to a wider developer audience.