From: David Howells <dhowells@redhat.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: dhowells@redhat.com, Matt Helsley <matthltc@us.ibm.com>,
Oleg Nesterov <oleg@redhat.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
ebiederm@xmission.com, hch@lst.de
Subject: Re: + mm-remove-struct-mm_struct-exe_file-et-al.patch added to -mm tree
Date: Wed, 01 Apr 2009 13:55:57 +0100 [thread overview]
Message-ID: <22191.1238590557@redhat.com> (raw)
In-Reply-To: <20090401011344.GB22398@x200.localdomain>
Alexey Dobriyan <adobriyan@gmail.com> wrote:
> and, as was mentioned, file is mapped low, so it'd be among the first VMAs.
Not so on NOMMU. The file is mapped wherever the allocator happens to throw up
a sufficient quantity of contiguous pages. It may not even be mapped in RAM.
David
next prev parent reply other threads:[~2009-04-01 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 23:44 + mm-remove-struct-mm_struct-exe_file-et-al.patch added to -mm tree akpm
2009-03-31 14:40 ` Oleg Nesterov
2009-04-01 0:32 ` Matt Helsley
2009-04-01 1:13 ` Alexey Dobriyan
2009-04-01 12:55 ` David Howells [this message]
2009-04-01 1:40 ` Oleg Nesterov
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=22191.1238590557@redhat.com \
--to=dhowells@redhat.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matthltc@us.ibm.com \
--cc=oleg@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.