From: Carsten Otte <cotte@freenet.de>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: David Woodhouse <dwmw2@infradead.org>,
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: Thu, 12 May 2005 11:10:47 +0200 [thread overview]
Message-ID: <42831D97.8000600@freenet.de> (raw)
In-Reply-To: <20050512085741.GA16361@wohnheim.fh-wedel.de>
Jörn Engel wrote:
> In principle, both the block device abstraction and the mtd
>
>abstraction fit your bill. But jffs2 doesn't, so no in-kernel fs
>could make use of a xip-aware mtd abstraction.
>
>
True. In fact I thought about an mtd device driver for our dcss
segments instead of a block device driver. A filesystem on top
of mtd that implements get_xip_page does the very same job.
But after I decided to build on the ext family, I discarded that
idea because ext does use the block device interface.
WARNING: multiple messages have this Message-ID (diff)
From: Carsten Otte <cotte@freenet.de>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: David Woodhouse <dwmw2@infradead.org>,
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: Thu, 12 May 2005 11:10:47 +0200 [thread overview]
Message-ID: <42831D97.8000600@freenet.de> (raw)
In-Reply-To: <20050512085741.GA16361@wohnheim.fh-wedel.de>
Jörn Engel wrote:
> In principle, both the block device abstraction and the mtd
>
>abstraction fit your bill. But jffs2 doesn't, so no in-kernel fs
>could make use of a xip-aware mtd abstraction.
>
>
True. In fact I thought about an mtd device driver for our dcss
segments instead of a block device driver. A filesystem on top
of mtd that implements get_xip_page does the very same job.
But after I decided to build on the ext family, I discarded that
idea because ext does use the block device interface.
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-05-12 9:14 UTC|newest]
Thread overview: 21+ 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 8:57 ` Jörn Engel
2005-05-12 9:10 ` Carsten Otte [this message]
2005-05-12 9:10 ` Carsten Otte
2005-05-12 9:43 ` David Woodhouse
2005-05-12 9:43 ` David Woodhouse
2005-06-01 9:33 ` Coywolf Qi Hunt
2005-06-01 9:33 ` Coywolf Qi Hunt
2005-06-01 11:31 ` Jörn Engel
2005-06-01 11:31 ` Jörn Engel
2005-06-01 10:12 ` Coywolf Qi Hunt
2005-06-01 12:06 ` Arnd Bergmann
2005-06-01 13:39 ` Jörn Engel
2005-06-01 13:39 ` Jörn Engel
2005-06-01 14:03 ` Carsten Otte
2005-06-01 14:03 ` Carsten Otte
2005-06-01 14:10 ` Jörn Engel
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=42831D97.8000600@freenet.de \
--to=cotte@freenet.de \
--cc=akpm@osdl.org \
--cc=dwmw2@infradead.org \
--cc=joern@wohnheim.fh-wedel.de \
--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 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.