public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Darwin Rambo <drambo@broadcom.com>
Cc: "dedekind@infradead.org" <dedekind@infradead.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Matthieu CASTET <matthieu.castet@parrot.com>,
	Adrian Hunter <adrian.hunter@nokia.com>
Subject: Re: UBIFS and hardware ECC of all FF pages of MLC NAND
Date: Tue, 29 Sep 2009 19:20:39 +0300	[thread overview]
Message-ID: <4AC233D7.6070502@gmail.com> (raw)
In-Reply-To: <B125D8217ABC4B43826503DE00A2D44910D7F2EAE3@SJEXCHCCR01.corp.ad.broadcom.com>

On 09/29/2009 07:13 PM, Darwin Rambo wrote:
> It is a bigger problem with 512K erase blocks. In this case, my
> 6MB jffs2 image grows to over 14MB ubifs image due to padding. There are about 12
> partial blocks with little data in the first few pages, and about 4 partial
> blocks at the end. 16 partial blocks is about 8 MB of overhead on 6MB of
> real content.

Well, of course I do not object if someone implements the optimization
you mentioned, but I do not have time to do this.

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

  reply	other threads:[~2009-09-29 16:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-18 21:31 UBIFS and hardware ECC of all FF pages of MLC NAND Darwin Rambo
2009-09-24 13:20 ` Adrian Hunter
2009-09-24 14:51   ` Artem Bityutskiy
2009-09-24 15:36   ` Matthieu CASTET
2009-09-25  7:05     ` Artem Bityutskiy
2009-09-29 13:26       ` Darwin Rambo
2009-09-29 15:42         ` Artem Bityutskiy
2009-09-29 16:13           ` Darwin Rambo
2009-09-29 16:20             ` Artem Bityutskiy [this message]
2009-09-29 17:03               ` Darwin Rambo
2009-10-11  8:39         ` Artem Bityutskiy
2009-10-11 14:38           ` Darwin Rambo
2009-10-11 15:04             ` Artem Bityutskiy
2009-10-11 17:36               ` Darwin Rambo

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=4AC233D7.6070502@gmail.com \
    --to=dedekind1@gmail.com \
    --cc=adrian.hunter@nokia.com \
    --cc=dedekind@infradead.org \
    --cc=drambo@broadcom.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=matthieu.castet@parrot.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