From: Christoph Lameter <cl@linux.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-rdma@vger.kernel.org,
Hugh Dickins <hughd@google.com>
Subject: Re: [RFC] mm: Distinguish between mlocked and pinned pages
Date: Thu, 18 Aug 2011 18:51:43 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1108181851100.11512@router.home> (raw)
In-Reply-To: <20110817155412.cc302033.akpm@linux-foundation.org>
On Wed, 17 Aug 2011, Andrew Morton wrote:
> Sounds reasonable. But how do we prevent future confusion? We should
> carefully define these terms in an obvious place, please.
Ok.
> > --- linux-2.6.orig/include/linux/mm_types.h 2011-08-10 14:08:42.000000000 -0500
> > +++ linux-2.6/include/linux/mm_types.h 2011-08-10 14:09:02.000000000 -0500
> > @@ -281,7 +281,7 @@ struct mm_struct {
> > unsigned long hiwater_rss; /* High-watermark of RSS usage */
> > unsigned long hiwater_vm; /* High-water virtual memory usage */
> >
> > - unsigned long total_vm, locked_vm, shared_vm, exec_vm;
> > + unsigned long total_vm, locked_vm, pinned_vm, shared_vm, exec_vm;
> > unsigned long stack_vm, reserved_vm, def_flags, nr_ptes;
> > unsigned long start_code, end_code, start_data, end_data;
> > unsigned long start_brk, brk, start_stack;
>
> This is an obvious place. Could I ask that you split all these up into
> one-definition-per-line and we can start in on properly documenting
> each field?
Will do that after the linuxcon.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-08-18 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 20:21 Christoph Lameter
2011-08-17 22:54 ` Andrew Morton
2011-08-18 23:51 ` Christoph Lameter [this message]
2011-08-23 14:59 ` Christoph Lameter
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=alpine.DEB.2.00.1108181851100.11512@router.home \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.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