public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Daniel Drake <dsd@laptop.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubifs: missing FAQ item regarding default compression options?
Date: Sun, 24 Jul 2011 10:28:45 +0300	[thread overview]
Message-ID: <1311492529.2855.2.camel@koala> (raw)
In-Reply-To: <CAGq3pz7XqJvapBQyiAuwvKMZekmXC-Nc4UugUB5H4ApHZo8aDw@mail.gmail.com>

On Sun, 2011-07-24 at 00:02 +0100, Daniel Drake wrote:
> Hi,
> 
> OLPC is looking more seriously at making the switch from jffs2 to
> ubifs. We did this for a few months but we found that ubifs has
> significantly higher (10-15%) disk space requirements for the same
> data, compared with jffs2. We switched back to jffs2 because of this,
> promising to look at ubifs again later (i.e. now).
> 
> What I didn't realise clearly at the time is that mkfs.jffs2 defaults
> to zlib compression, and mkfs.ubifs defaults to LZO compression. So,
> this was not a fair test. If I switch ubifs to zlib compression, it
> produces results very similar to jffs.
> 
> For example, for one OS image, mkfs.jffs2 + sumtool produced a 664mb
> file. mkfs.ubifs (with zlib selected) + ubinize created a 668mb image
> of the same data - very comparable.
> 
> Should this be a FAQ entry? Others who aren't aware of this difference
> in default compression options may run into the same non-issue.

Hi Daniel,

sure, send a patch against the mtd-www repo:

git://git.infradead.org/mtd-www.git

and add this piece of information. The web site is very simple and
you'll find out how to edit it easily. Then type "make" to build it.

-- 
Best Regards,
Artem Bityutskiy (Битюцкий Артём)

      reply	other threads:[~2011-07-24  7:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-23 23:02 ubifs: missing FAQ item regarding default compression options? Daniel Drake
2011-07-24  7:28 ` Artem Bityutskiy [this message]

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=1311492529.2855.2.camel@koala \
    --to=dedekind1@gmail.com \
    --cc=dsd@laptop.org \
    --cc=linux-mtd@lists.infradead.org \
    /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