Well, what's the alternative? Invent a new type of memory reservations specifically to account for tmpfs/ramfs mounts? That'd violate your own stated desired goal of
> The OS should just expose a counter for available memory instead of having applications understand every type of memory reservation.
I don’t see how it contradicts my goal. I want memory counters that abstract away kernel behavior that the application has no business accounting for.