[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: [BUG] table will be garbage collected multiple times
- From: Tim Hill <drtimhill@...>
- Date: Tue, 20 Nov 2018 13:38:44 -0800
> On Nov 20, 2018, at 10:17 AM, Philippe Verdy <firstname.lastname@example.org> wrote:
> generations identifiable as any object;
> This would be useful for example to create different pools, notably for caches (Lua appliations would be able to manage efficiently their "cache eviction policy", which is something very important to avoid DOS attacks that attempt to clear caches used by concurrent threads, and to avoid time attacks similar to Meltdown, measuring the time to honor requests, which is shorter if an object is still in cache than when it is not because the object has to be reconstructed, meaning that a third party can know if an object was recently used by another thread).
In al this long thread, what specific problem are you trying to solve? It’s been established that the current GC behavior is by design and not a bug. And the various proposals around changes to __gc don’t seem to offer any new functionality.