[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6934efce0808211232i21fcf347vb6baa6502246adb2@mail.gmail.com>
Date: Thu, 21 Aug 2008 12:32:13 -0700
From: "Jared Hulbert" <jaredeh@...il.com>
To: "Frans Meulenbroeks" <fransmeulenbroeks@...il.com>
Cc: Linux-kernel@...r.kernel.org, linux-embedded@...r.kernel.org,
linux-mtd <linux-mtd@...ts.infradead.org>,
"Jörn Engel" <joern@...fs.org>,
tim.bird@...sony.com, cotte@...ibm.com, nickpiggin@...oo.com.au
Subject: Re: [PATCH 00/10] AXFS: Advanced XIP filesystem
> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists