From: Andrew Crawford <acrawford@ieee.org>
To: linux-mm@kvack.org
Subject: Re: The long, long life of an inactive_dirty page
Date: Wed, 12 May 2004 12:18:47 -0700 (PDT) [thread overview]
Message-ID: <200405121918.i4CJIlF6095429@newsguy.com> (raw)
> That information is not achievable in a reliable way, ever. Simply because
> it takes a not-even-near-inifintely small amount of time to gather all the
> stats, during which the other cpu can change all the underlying data away
> under your nose.
Although that is of course true, it's also well understood and a factor with
any operating system. Nevertheless, it would be useful to have a picture of
how much memory is available right now. An inaccurate (within reason)
indication *would* be better than none at all.
Just to gather opinions, and since we've been having a bit of a heated
discussion about it here at work, how would you good people define "available
RAM"? and which memory metrics would make it up?
My definition would be "RAM which can be allocated and used without the need
to write any pages". I.e if the memory needs laundered first but no actual
writes need to be done, that's fine and I'll count it as available.
So I'd be counting
Free
+
Inactive_Clean
+
The clean part of inactive_dirty (which can't be measured at present)
Is there anything else that should be on there?
Cheers,
Andrew
--
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:"aart@kvack.org"> aart@kvack.org </a>
next reply other threads:[~2004-05-12 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 19:18 Andrew Crawford [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-12 18:24 Andrew Crawford
2004-05-12 18:46 ` Arjan van de Ven
2004-05-12 15:28 Andrew Crawford
2004-05-12 16:29 ` Arjan van de Ven
2004-05-12 14:11 Andrew Crawford
2004-05-12 14:51 ` Arjan van de Ven
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=200405121918.i4CJIlF6095429@newsguy.com \
--to=acrawford@ieee.org \
--cc=linux-mm@kvack.org \
/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