On Tue, 16 Feb 2016, Vladimir Davydov wrote:
On Tue, Feb 16, 2016 at 02:58:04AM +, Nag Avadhanam (nag) wrote:
We have a class of platforms that are essentially swap-less embedded
systems that have limited memory resources (2GB and less).
There is a need to implement early alerts (before
On Mon, 15 Feb 2016, Dave Chinner wrote:
On Mon, Feb 15, 2016 at 03:52:31PM -0800, Daniel Walker wrote:
On 02/15/2016 03:05 PM, Dave Chinner wrote:
What you are proposing isn't accurate, either, because it will be
stale by the time the inode cache traversal is completed and the
count returned
On Mon, 15 Feb 2016, Dave Chinner wrote:
On Tue, Feb 16, 2016 at 02:58:04AM +, Nag Avadhanam (nag) wrote:
Its the calculation of the # of bytes of non-reclaimable file system cache
pages that has been troubling us. We do not want to count inactive file
pages (of programs/binaries
On Tue, 16 Feb 2016, Vladimir Davydov wrote:
On Tue, Feb 16, 2016 at 02:58:04AM +, Nag Avadhanam (nag) wrote:
We have a class of platforms that are essentially swap-less embedded
systems that have limited memory resources (2GB and less).
There is a need to implement early alerts (before
On Mon, 15 Feb 2016, Dave Chinner wrote:
On Mon, Feb 15, 2016 at 03:52:31PM -0800, Daniel Walker wrote:
On 02/15/2016 03:05 PM, Dave Chinner wrote:
What you are proposing isn't accurate, either, because it will be
stale by the time the inode cache traversal is completed and the
count returned
On Mon, 15 Feb 2016, Dave Chinner wrote:
On Tue, Feb 16, 2016 at 02:58:04AM +, Nag Avadhanam (nag) wrote:
Its the calculation of the # of bytes of non-reclaimable file system cache
pages that has been troubling us. We do not want to count inactive file
pages (of programs/binaries
We have a class of platforms that are essentially swap-less embedded
systems that have limited memory resources (2GB and less).
There is a need to implement early alerts (before the OOM killer kicks in)
based on the current memory usage so admins can take appropriate steps (do
not initiate
We have a class of platforms that are essentially swap-less embedded
systems that have limited memory resources (2GB and less).
There is a need to implement early alerts (before the OOM killer kicks in)
based on the current memory usage so admins can take appropriate steps (do
not initiate
8 matches
Mail list logo
