From: "Lindsay Roberts" <lindsay.roberts.os@gmail.com>
To: "Matt Mackall" <mpm@selenic.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
celinux-dev@tree.celinuxforum.org
Subject: Re: [PATCH] fs: Add romfs version 2
Date: Wed, 18 Jul 2007 13:16:24 +1000 [thread overview]
Message-ID: <8734b7880707172016v530ce775p108910f7baf9de8e@mail.gmail.com> (raw)
In-Reply-To: <20070717192100.GE11166@waste.org>
On 7/18/07, Matt Mackall <mpm@selenic.com> wrote:
> > > * Adds new derivative of romfs filesystem (rom2fs) with
> > > block aligned regular file data to bring performance
> > > parity with ext2/3. This is about 225% of the read
> > > speed of the existing romfs.
>
> Doesn't that make these filesystems much bigger? By, on average, .5k
> per file? Or, if I'm understanding things correctly, ~1k?
Yes, my experience has been that it has been almost chillingly close
to .5k per regular file increase in partition size. I know in
applications in which size is utterly critical this may be slightly
unattractive, but in cases where romfs is chosen for its byte
reproducibility and read-only nature the size/performance tradeoff is
fairly advantageous.
next prev parent reply other threads:[~2007-07-18 3:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 6:01 Lindsay Roberts
2007-07-17 8:36 ` Andrew Morton
2007-07-17 19:21 ` Matt Mackall
2007-07-18 3:16 ` Lindsay Roberts [this message]
2007-07-18 17:02 ` Tim Bird
2007-07-25 7:28 ` [Celinux-dev] " Greg Ungerer
2007-07-25 18:40 ` Pavel Machek
2007-08-06 7:43 ` Lindsay Roberts
2007-08-06 17:20 ` Matt Mackall
2007-07-30 18:12 ` Phillip Susi
2007-07-30 18:29 ` Rene Herman
2007-08-06 19:41 ` Sergey Vlasov
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=8734b7880707172016v530ce775p108910f7baf9de8e@mail.gmail.com \
--to=lindsay.roberts.os@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=celinux-dev@tree.celinuxforum.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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
all inboxes | Powered by JetHome®