mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Phillip Susi <psusi@cfl.rr.com>,
	Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Execute in place
Date: Wed, 2 May 2007 16:22:43 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705021616260.31229@blonde.wat.veritas.com> (raw)
In-Reply-To: <20070502143839.GA31961@atjola.homenet>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1218 bytes --]

On Wed, 2 May 2007, Björn Steinbrink wrote:
> On 2007.05.02 15:04:44 +0100, Hugh Dickins wrote:
> > On Tue, 1 May 2007, Phillip Susi wrote:
> > > I seem to remember seeing some patches go by at some point that
> > > allowed one of the rom type embeded system filesystems to directly
> > > execute binaries out of the original rom memory rather than copying
> > > them to ram first, then executing from there.  I was wondering if
> > > rootfs or tmpfs support such execute in place today, or if binaries
> > > executed from there have their code segments duplicated in ram?
> > 
> > Only ext2 supports it today: see Documentation/filesystems/xip.txt
> 
> As I understand it, xip avoids the page cache copy. But tmpfs already
> lives in the page cache (or swap), so avoiding that "copy" is
> impossible. But I always expected tmpfs to implicitly due its own kind
> of xip, i.e. that it doesn't have to store its stuff in the page cache
> twice. Are you saying that this isn't true?

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.

Hugh

  reply	other threads:[~2007-05-02 15:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
2007-05-02 23:11 Al Boldi
2007-05-03  7:31 ` 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

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.0705021616260.31229@blonde.wat.veritas.com \
    --to=hugh@veritas.com \
    --cc=B.Steinbrink@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=psusi@cfl.rr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®