From: Coywolf Qi Hunt <coywolf@gmail.com>
To: cotte@freenet.de
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
schwidefsky@de.ibm.com, akpm@osdl.org
Subject: Re: [RFC/PATCH 0/5] add execute in place support
Date: Wed, 1 Jun 2005 18:12:55 +0800 [thread overview]
Message-ID: <2cd57c9005060103122b2bae36@mail.gmail.com> (raw)
In-Reply-To: <428216DF.8070205@de.ibm.com>
On 5/11/05, Carsten Otte <cotte@de.ibm.com> wrote:
> Folks,
>
> this is the intro to a small series of patches that introduce execute
> in place into the I/O stack. File I/O to memory-backed block
> devices is performed directly, bypassing the page cache and io
> schedulers. On s390, we use this for block devices based on shared
> memory between multiple virtual machines. This is also useful on
> embedded systems where the block device is located on a flash chip.
> This work is a result of a prior discussion with Andrew Morton
> about my first implementation which basically was a filesystem
> derived from ext2.
>
> As I'd like to aim for integration into -mm and vanilla later on,
> I'd like to encourage everyone to give it a read and provide
> feedback. All patches apply against git-head as of today.
I feel the name "execute in place" misleading. This is not the real
XIP, IMHO. Invent another term or be tolerant?
--
Coywolf Qi Hunt
http://ahbl.org/~coywolf/
next prev parent reply other threads:[~2005-06-01 10:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 14:29 [RFC/PATCH 0/5] add execute in place support Carsten Otte
2005-05-11 16:19 ` David Woodhouse
2005-05-11 16:35 ` Carsten Otte
2005-05-12 8:57 ` Jörn Engel
2005-05-12 9:10 ` Carsten Otte
2005-05-12 9:43 ` David Woodhouse
2005-06-01 9:33 ` Coywolf Qi Hunt
2005-06-01 11:31 ` Jörn Engel
2005-06-01 10:12 ` Coywolf Qi Hunt [this message]
2005-06-01 12:06 ` Arnd Bergmann
2005-06-01 13:39 ` Jörn Engel
2005-06-01 14:03 ` Carsten Otte
2005-06-01 14:10 ` Jörn Engel
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=2cd57c9005060103122b2bae36@mail.gmail.com \
--to=coywolf@gmail.com \
--cc=akpm@osdl.org \
--cc=cotte@freenet.de \
--cc=coywolf@lovecn.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.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