From: Artem Bityutskiy <dedekind1@gmail.com>
To: Nicholas <ciliwung36@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBI memory usage on large page nand
Date: Sun, 17 Apr 2011 12:16:14 +0300 [thread overview]
Message-ID: <1303031774.2308.13.camel@koala> (raw)
In-Reply-To: <BANLkTin=dfsO9N02oVZg=kU3ghfymbzJWA@mail.gmail.com>
On Sun, 2011-04-17 at 17:03 +0800, Nicholas wrote:
> Dear Artem,
>
> Thanks for the advices. I'll try start for UBI first.
>
> Reducing peb_buf would mean i need to modify the ubi IO for read/write.
> As i know, ubi did an erase for a whole block before start writing,
>
> Please correct me if i've written in a wrong way.
Yes, when you investigate the code, you'll even find that if extra self
checks are enabled, UBI will verify that the area it writes to contains
only 0xFFs - it will read the area, compare with 0xFFs, and if all bytes
are 0xFFs it will proceed, otherwise it will shout loudly. See:
ubi_io_write() - all writes go through this function, and
ubi_dbg_check_all_ff - does the verification I talked about, but only in
debugging mode, because it is too costly to do it in production mode.
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2011-04-17 9:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=GsmJOjurETG930t-TW7uXLR1M6yKXWBSk7ebV@mail.gmail.com>
2011-03-31 3:07 ` UBI memory usage on large page nand Nicholas
2011-04-01 15:31 ` Artem Bityutskiy
2011-04-15 9:23 ` Nicholas
2011-04-15 13:13 ` Artem Bityutskiy
2011-04-15 13:17 ` Artem Bityutskiy
2011-04-15 13:24 ` Artem Bityutskiy
2011-04-17 9:03 ` Nicholas
2011-04-17 9:16 ` Artem Bityutskiy [this message]
2011-04-18 8:29 ` Nicholas
2011-04-18 8:39 ` Artem Bityutskiy
2011-04-20 3:19 ` Nicholas
2011-04-20 7:30 ` Artem Bityutskiy
2011-08-17 6:35 ` Nicholas
2011-08-20 5:17 ` Artem Bityutskiy
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=1303031774.2308.13.camel@koala \
--to=dedekind1@gmail.com \
--cc=ciliwung36@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.