Pratik Sampat <psampat@xxxxxxxxxxxxx> writes: > On 18/10/21 9:59 pm, Tejun Heo wrote: >> (cc'ing Johannes for memory sizing part) >> >> For memory, it's even trickier because in a lot of cases it's impossible to >> tell how much memory is actually available without trying to use them as >> active workingset can only be learned by trying to reclaim memory. > > Restrictions for memory are even more complicated to model as you have > pointed out as well. For memory sizing we currently have MemAvailable in /proc/meminfo which makes a global guess at that. We still need roughly that same approximation from an applications perspective that takes cgroups into account. There was another conversation not too long ago and it was tenatively agreed that it could make sense to provide such a number. However it was very much requested that an application that would actually use that number be found so it would be possible to tell what makes a difference in practice rather than what makes a difference in theory. Eric
