From: Vladimir Davydov <vdavydov@virtuozzo.com>
To: "Nag Avadhanam (nag)" <nag@cisco.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
"Daniel Walker (danielwa)" <danielwa@cisco.com>,
Dave Chinner <david@fromorbit.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
"Khalid Mughal (khalidm)" <khalidm@cisco.com>,
"xe-kernel@external.cisco.com" <xe-kernel@external.cisco.com>,
"dave.hansen@intel.com" <dave.hansen@intel.com>,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
"riel@redhat.com" <riel@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] kernel: fs: drop_caches: add dds drop_caches_count
Date: Tue, 16 Feb 2016 11:43:46 +0300 [thread overview]
Message-ID: <20160216084346.GA8511@esperanza> (raw)
In-Reply-To: <D2E7B337.D5404%nag@cisco.com>
On Tue, Feb 16, 2016 at 02:58:04AM +0000, 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 the OOM killer kicks in)
> based on the current memory usage so admins can take appropriate steps (do
> not initiate provisioning operations but support existing services,
> de-provision certain services, etc. based on the extent of memory usage in
> the system) .
>
> There is also a general need to let end users know the available memory so
> they can determine if they can enable new services (helps in planning).
>
> These two depend upon knowing approximate (accurate within few 10s of MB)
> memory usage within the system. We want to alert admins before system
> exhibits any thrashing behaviors.
Have you considered using /proc/kpageflags for counting such pages? It
should already export all information about memory pages you might need,
e.g. which pages are mapped, which are anonymous, which are inactive,
basically all page flags and even more. Moreover, you can even determine
the set of pages that are really read/written by processes - see
/sys/kernel/mm/page_idle/bitmap. On such a small machine scanning the
whole pfn range should be pretty cheap, so you might find this API
acceptable.
Thanks,
Vladimir
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-02-16 8:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 20:14 [PATCH] kernel: fs: drop_caches: add dds drop_caches_count Daniel Walker
2016-02-14 21:18 ` Dave Chinner
2016-02-15 18:19 ` Daniel Walker
2016-02-15 23:05 ` Dave Chinner
2016-02-15 23:52 ` Daniel Walker
2016-02-16 0:45 ` Theodore Ts'o
2016-02-16 2:58 ` Nag Avadhanam (nag)
2016-02-16 5:38 ` Dave Chinner
2016-02-16 7:14 ` Nag Avadhanam
2016-02-16 8:35 ` Dave Chinner
2016-02-16 8:43 ` Vladimir Davydov [this message]
2016-02-16 18:37 ` Nag Avadhanam
2016-02-16 5:28 ` Dave Chinner
2016-02-16 5:57 ` Nag Avadhanam
2016-02-16 8:22 ` Dave Chinner
2016-02-16 16:12 ` Rik van Riel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160216084346.GA8511@esperanza \
--to=vdavydov@virtuozzo.com \
--cc=corbet@lwn.net \
--cc=danielwa@cisco.com \
--cc=dave.hansen@intel.com \
--cc=david@fromorbit.com \
--cc=hannes@cmpxchg.org \
--cc=khalidm@cisco.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nag@cisco.com \
--cc=riel@redhat.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=xe-kernel@external.cisco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).