From: Al Boldi <a1426z@gawab.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Execute in place
Date: Thu, 3 May 2007 02:11:36 +0300 [thread overview]
Message-ID: <200705030211.36293.a1426z@gawab.com> (raw)
Hugh Dickins wrote:
> On Wed, 2 May 2007, Phillip Susi wrote:
> > Hugh Dickins wrote:
> > > tmpfs doesn't store its stuff in the page cache twice: that's true,
> > > and I didn't mean to imply otherwise. But tmpfs doesn't contain any
> > > support for rom memory: you'd have to copy from rom to tmpfs to use
> > > it.
> >
> > The question is, when you execute a binary on tmpfs, does its code
> > segment get mapped directly where it's at in the buffer cache, or does
> > it get copied to another page for the executing process? At least,
> > assuming this is possible due to the vma and file offsets of the segment
> > being aligned.
>
> Its pages are mapped directly into the executing process, without copying.
Thank GOD! Boy, was I worried there for a second.
Now, if there were only an easy way to make tmpfs persistent?
Thanks!
--
Al
next reply other threads:[~2007-05-02 23:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 23:11 Al Boldi [this message]
2007-05-03 7:31 ` Execute in place Dmitry Krivoschekov
2007-05-03 11:33 ` Al Boldi
2007-05-03 17:38 ` Dmitry Krivoschekov
2007-05-07 16:46 ` H. Peter Anvin
2007-05-07 19:37 ` Al Boldi
2007-05-07 19:41 ` H. Peter Anvin
2007-05-07 20:56 ` Al Boldi
2007-05-08 6:06 ` H. Peter Anvin
2007-05-08 11:36 ` Al Boldi
2007-05-08 11:37 ` H. Peter Anvin
2007-05-08 12:02 ` Al Boldi
-- strict thread matches above, loose matches on Subject: below --
2007-05-01 21:55 Phillip Susi
2007-05-02 14:04 ` Hugh Dickins
2007-05-02 14:38 ` Björn Steinbrink
2007-05-02 15:22 ` Hugh Dickins
2007-05-02 19:30 ` Phillip Susi
2007-05-02 20:34 ` Hugh Dickins
2007-05-03 11:38 ` Erik Mouw
2007-05-03 15:37 ` Jörn Engel
2007-05-03 12:12 ` Robin Getz
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=200705030211.36293.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=linux-kernel@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