From: "Bart Van Assche" <bart.vanassche@gmail.com>
To: Albert Cahalan <acahalan@cs.uml.edu>
Cc: linux-mm@kvack.org, Mel Gorman <mel@csn.ul.ie>
Subject: Re: Synchronization of the procps tools with /proc/meminfo
Date: Tue, 19 Feb 2008 19:59:30 +0100 [thread overview]
Message-ID: <e2e108260802191059q17bceccdsb8e43dd043295a0b@mail.gmail.com> (raw)
In-Reply-To: <787b0d920802191053pea784fdycd3b5119cfb886a@mail.gmail.com>
On Feb 19, 2008 7:53 PM, Albert Cahalan <acahalan@cs.uml.edu> wrote:
> On Feb 18, 2008 10:55 AM, Bart Van Assche <bart.vanassche@gmail.com> wrote:
>
> > This leads me to the question: if the layout of /proc/meminfo changes,
> > who communicates these changes to the procps maintainers ?
>
> Nobody ever informs me. :-(
That's very unfortunate.
But how should we proceed ? There is not only the SReclaimable field
that was added to /proc/meminfo, there is also the NFS_Unstable field.
I'm not sure whether that last one counts as reclaimable.
Note: Mel Gorman, who's also in CC, is on holiday but will jump in on
this discussion as soon as he's back from holiday.
Bart Van Assche.
--
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:[~2008-02-19 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 15:55 Synchronization of the procps tools with /proc/meminfo Bart Van Assche
2008-02-19 18:53 ` Albert Cahalan
2008-02-19 18:59 ` Bart Van Assche [this message]
2008-03-08 9:35 ` Bart Van Assche
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=e2e108260802191059q17bceccdsb8e43dd043295a0b@mail.gmail.com \
--to=bart.vanassche@gmail.com \
--cc=acahalan@cs.uml.edu \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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).