linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jared Hulbert" <jaredeh@gmail.com>
To: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
Cc: Linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org,
	linux-mtd <linux-mtd@lists.infradead.org>,
	"Jörn Engel" <joern@logfs.org>,
	tim.bird@am.sony.com, cotte@de.ibm.com, nickpiggin@yahoo.com.au
Subject: Re: [PATCH 00/10] AXFS: Advanced XIP filesystem
Date: Thu, 21 Aug 2008 12:32:13 -0700	[thread overview]
Message-ID: <6934efce0808211232i21fcf347vb6baa6502246adb2@mail.gmail.com> (raw)
In-Reply-To: <ac9c93b10808202332n2654884eh877848df2da59f20@mail.gmail.com>

> Jared, nice work!

Thanks.

> A few questions:

I meant to address these before.  Sorry.

> - how does this benchmark compared to cramfs and squashfs in a NAND-only system
>  (or is it just not a good plan to use this with NAND-only (of course
> I won't get XIP with NAND, I understand that)

I don't know, I'm interested to find out.  I just benchmarked that.
Actually it should work very well as a NAND-only fs.  Also you do get
something like XIP with NAND.  If you boot an XIP AXFS image on NAND
or a blkdev it will copy that XIP region into RAM and "XIP" it from
there.  I think this will make it very good for LiveCD's.  Though we
just (minutes ago) realized our testing of that feature was flawed, so
no guarantees.

> - would axfs be suitable as a filesystem on a ram disk?

It could be.  I plan on implementing support for brd.  That might work nicely.

  reply	other threads:[~2008-08-21 19:32 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21  5:44 [PATCH 00/10] AXFS: Advanced XIP filesystem Jared Hulbert
2008-08-21  6:32 ` Frans Meulenbroeks
2008-08-21 19:32   ` Jared Hulbert [this message]
2008-08-22  2:04     ` Nick Piggin
2008-08-21  8:39 ` Dave Chinner
2008-08-21 14:19   ` Jared Hulbert
2008-08-21 14:31     ` Leon Woestenberg
2008-08-21 14:42       ` Jared Hulbert
2008-08-21 14:49       ` Geert Uytterhoeven
2008-08-21 10:25 ` Carsten Otte
2008-08-21 10:43   ` Nick Piggin
2008-08-21 12:53     ` Arnd Bergmann
2008-08-21 14:12       ` Jared Hulbert
2008-08-21 14:14         ` Arnd Bergmann
2008-08-21 14:13     ` Jared Hulbert
2008-08-22  2:32       ` Nick Piggin
2008-08-21 14:30   ` Jared Hulbert
2008-08-21 11:07 ` Jamie Lokier
2008-08-21 14:11   ` Jared Hulbert
2008-08-22  0:12     ` Greg Ungerer
2008-08-22  2:48       ` Jared Hulbert
2008-08-25  6:35         ` Greg Ungerer
2008-08-25 11:43           ` Jamie Lokier
2008-08-25 14:02             ` Greg Ungerer
2008-08-22 18:13       ` Jamie Lokier
2008-08-22 18:16         ` Jared Hulbert
2008-08-22 18:37           ` Jamie Lokier
2008-08-22 18:43             ` Jamie Lokier
2008-09-12 21:52               ` Jared Hulbert
2008-09-15 16:34                 ` Jamie Lokier
2008-09-15 19:43                   ` Jared Hulbert
2008-09-19 19:20                     ` Trent Piepho
2008-09-16  6:57                   ` Ricard Wanderlof
2008-09-16 15:30                     ` Jared Hulbert
2008-09-12 20:17             ` Jared Hulbert
2008-09-15 16:40               ` Jamie Lokier
2008-08-21 23:46   ` Greg Ungerer
2008-08-22 18:10     ` Jamie Lokier
2008-08-22 14:54 ` Geert Uytterhoeven
2008-08-22 15:19   ` Arnd Bergmann
2008-08-22 16:51   ` Jared Hulbert
2008-08-25  9:37     ` Geert Uytterhoeven
2008-08-25 10:52       ` Carsten Otte
2008-08-25 12:16     ` David Woodhouse
2008-08-28 15:40     ` Geert Uytterhoeven
2008-09-02 15:37       ` Geert Uytterhoeven
2008-09-02 16:44         ` Jared Hulbert
2008-09-02 17:15           ` Jörn Engel
2008-09-02 17:47             ` Jared Hulbert
2008-09-02 18:33           ` Geert Uytterhoeven
2008-08-22 22:09   ` Will Marone
2008-08-25  7:23     ` Geert Uytterhoeven

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=6934efce0808211232i21fcf347vb6baa6502246adb2@mail.gmail.com \
    --to=jaredeh@gmail.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=cotte@de.ibm.com \
    --cc=fransmeulenbroeks@gmail.com \
    --cc=joern@logfs.org \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=tim.bird@am.sony.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;
as well as URLs for NNTP newsgroup(s).