From: Arnd Bergmann <arnd@arndb.de>
To: "Jared Hulbert" <jaredeh@gmail.com>
Cc: "Phillip Lougher" <phillip@lougher.demon.co.uk>,
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 06/10] AXFS: axfs_super.c
Date: Fri, 22 Aug 2008 18:52:37 +0200 [thread overview]
Message-ID: <200808221852.38950.arnd@arndb.de> (raw)
In-Reply-To: <6934efce0808212005h30fa16d8w48833e8a0becfd8c@mail.gmail.com>
On Friday 22 August 2008, Jared Hulbert wrote:
> > This implies for block devices that the entire filesystem metadata has to be
> > cached in RAM. This severely limits the size of AXFS filesystems when using
> > block devices, or the else memory usage will be excessive.
>
> This is where 64bit squashfs could be a better fit.
Is this the only place where squashfs has a significant advantage?
If so, you might want to change it in axfs eventually to make the
decision easier for users ;-)
It certainly sounds like something for your medium-term TODO list,
although I wouldn't think of it as a show-stopper.
Arnd <><
next prev parent reply other threads:[~2008-08-22 16:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 5:45 [PATCH 06/10] AXFS: axfs_super.c Jared Hulbert
2008-08-21 8:55 ` Carsten Otte
2008-08-21 9:04 ` Sven Wegener
2008-08-21 11:27 ` Sven Wegener
2008-08-21 14:54 ` Sven Wegener
2008-08-22 1:43 ` Phillip Lougher
2008-08-22 3:05 ` Jared Hulbert
2008-08-22 16:52 ` Arnd Bergmann [this message]
2008-08-22 17:37 ` Phillip Lougher
2008-08-22 17:42 ` Jared Hulbert
2008-08-22 19:49 ` Arnd Bergmann
2008-08-22 17:43 ` Jared Hulbert
2008-08-22 19:37 ` Arnd Bergmann
2008-08-22 12:07 ` Bernhard Reutner-Fischer
2008-10-29 13:59 ` 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=200808221852.38950.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=Linux-kernel@vger.kernel.org \
--cc=cotte@de.ibm.com \
--cc=jaredeh@gmail.com \
--cc=joern@logfs.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nickpiggin@yahoo.com.au \
--cc=phillip@lougher.demon.co.uk \
--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