From: Hugh Dickins <hugh@veritas.com>
To: Dave McCracken <dave.mccracken@oracle.com>
Cc: herbert.van.den.bergh@oracle.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] include private data mappings in RLIMIT_DATA limit
Date: Tue, 10 Jul 2007 19:06:15 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707101857310.20758@blonde.wat.veritas.com> (raw)
In-Reply-To: <200707101219.29743.dave.mccracken@oracle.com>
On Tue, 10 Jul 2007, Dave McCracken wrote:
> On Tuesday 10 July 2007, Hugh Dickins wrote:
> > > >
> > > > This brings the Linux behavior in line with what is documented in the
> > > > POSIX man page for setrlimit(3p).
> >
> > Which says malloc() can fail from it, but conspicuously not that mmap()
> > can fail from it: unlike the RLIMIT_AS case. Would we be better off?
>
> True. But keep in mind that when POSIX was written mmap() was new and shiny
> and pretty much only used for shared mappings, and definitely not used by
> malloc().
Well, my bookmark is to SUSv3, which I think is equivalent these days?
And that specifically says malloc() or mmap() in the RLIMIT_AS case,
but only malloc() in the RLIMIT_DATA case. We're wrong either way.
> Given that RLIMIT_DATA is pretty much meaningless in current kernels, I would
> put forward the argument that this change is extremely unlikely to break
> anything because no one is currently setting it to anything other than
> unlimited. Adding this feature would give administrators another tool, a way
> to control the private data size of a process without restricting its ability
> to attach to large shared mappings.
That may be a good argument (though "extremely unlikely to break"s
have a nasty habit of biting). I'd still say that the contribution
to Committed_AS is more appropriate and more useful here.
> > That change to /proc/PID/status VmData:
> > - data = mm->total_vm - mm->shared_vm - mm->stack_vm;
> > + data = mm->total_vm - mm->shared_vm - mm->stack_vm - mm->exec_vm;
> > looks plausible, but isn't exec_vm already counted as shared_vm,
> > so now being doubly subtracted? Besides which, we wouldn't want
> > to change those numbers again without consulting Albert.
>
> As I recall, this was added after Herbert discovered that exec_vm is not
> counted as shared_vm. It's actually mapped as private/readonly.
Mapped private readonly yes, but vm_stat_account() says
if (file) {
mm->shared_vm += pages;
if ((flags & (VM_EXEC|VM_WRITE)) == VM_EXEC)
mm->exec_vm += pages;
Hugh
--
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:[~2007-07-10 18:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 0:43 Herbert van den Bergh
2007-07-10 0:54 ` Dave McCracken
2007-07-10 16:58 ` Hugh Dickins
2007-07-10 17:19 ` Dave McCracken
2007-07-10 18:06 ` Hugh Dickins [this message]
2007-07-10 19:12 ` Dave McCracken
2007-07-10 19:42 ` Hugh Dickins
2007-07-10 20:09 ` Herbert van den Bergh
2007-07-13 19:18 ` Hugh Dickins
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=Pine.LNX.4.64.0707101857310.20758@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=akpm@linux-foundation.org \
--cc=dave.mccracken@oracle.com \
--cc=herbert.van.den.bergh@oracle.com \
--cc=linux-kernel@vger.kernel.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