From: Artem Bityutskiy <dedekind1@gmail.com>
To: Richard Genoud <richard.genoud@gmail.com>
Cc: linux-mtd@lists.infradead.org,
Shmulik Ladkani <shmulik.ladkani@gmail.com>
Subject: Re: [PATCH v3 0/6] UBI: add max_beb_per1024 parameter / ioctl
Date: Thu, 23 Aug 2012 17:45:53 +0300 [thread overview]
Message-ID: <1345733153.2848.244.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CACQ1gAhs6E5jHGnTy1RhbnuzKq7uAJk0DeHfi0k73jC_8noiAg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 864 bytes --]
On Thu, 2012-08-23 at 15:13 +0200, Richard Genoud wrote:
> I could do some more tests with the final version.
Thanks!
> I guess that the documentation to update is there:
> http://www.linux-mtd.infradead.org/doc/ubi.html
Yes, a separate section about how UBI reserves eraseblocks for bad PEBs
handling is needed.
> The message commit of dccaefbd68ce0c4d83f1d57667726868bdc03cce (UBI:
> use the whole MTD device size to get bad_peb_limit)
> could be a start for the "Why?"
Sure.
Additionally, all places where we mention 2% should be amended
correspondingly. I guess this commit can be used to locate the places:
http://git.infradead.org/mtd-www.git/commit/2b91234cf1dd9968d18679b19d7dbe22b6508cff
Also, this section should be amended:
http://www.linux-mtd.infradead.org/doc/ubi.html#L_overhead
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-08-23 14:43 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 16:00 [PATCH v3 0/6] UBI: add max_beb_per1024 parameter / ioctl Richard Genoud
2012-08-20 16:00 ` [PATCH v3 1/6] UBI: prepare for max_beb_per1024 module parameter addition Richard Genoud
2012-08-20 19:01 ` Artem Bityutskiy
2012-08-20 16:00 ` [PATCH v3 2/6] UBI: change CONFIG_MTD_UBI_BEB_LIMIT range Richard Genoud
2012-08-20 19:03 ` Artem Bityutskiy
2012-08-20 16:00 ` [PATCH v3 3/6] UBI: check max_beb_per1024 value in ubi_attach_mtd_dev Richard Genoud
2012-08-20 19:19 ` Artem Bityutskiy
2012-08-20 16:00 ` [PATCH v3 4/6] UBI: replace MTD_UBI_BEB_LIMIT with module parameter Richard Genoud
2012-08-21 13:54 ` Artem Bityutskiy
2012-08-22 8:32 ` Richard Genoud
2012-08-22 8:49 ` Artem Bityutskiy
2012-08-22 12:09 ` Richard Genoud
2012-08-22 12:16 ` Artem Bityutskiy
2012-08-20 16:00 ` [PATCH v3 5/6] UBI: add ioctl for max_beb_per1024 Richard Genoud
2012-08-21 19:34 ` Artem Bityutskiy
2012-08-20 16:00 ` [PATCH v3 6/6] UBI: drop CONFIG_MTD_UBI_BEB_LIMIT Richard Genoud
2012-08-21 19:34 ` Artem Bityutskiy
2012-08-23 10:10 ` [PATCH v3 0/6] UBI: add max_beb_per1024 parameter / ioctl Artem Bityutskiy
2012-08-23 10:36 ` Shmulik Ladkani
2012-08-23 11:01 ` Richard Genoud
2012-08-23 12:30 ` Artem Bityutskiy
2012-08-23 12:44 ` Shmulik Ladkani
2012-08-23 12:58 ` Artem Bityutskiy
2012-08-23 13:13 ` Richard Genoud
2012-08-23 14:45 ` Artem Bityutskiy [this message]
2012-08-31 14:46 ` Richard Genoud
2012-09-03 8:00 ` Artem Bityutskiy
2012-09-03 10:57 ` Richard Genoud
2012-09-03 11:53 ` Artem Bityutskiy
2012-09-03 13:14 ` Richard Genoud
2012-09-03 13:31 ` Artem Bityutskiy
2012-09-03 13:37 ` Richard Genoud
2012-09-03 14:32 ` Artem Bityutskiy
2012-09-03 14:33 ` Artem Bityutskiy
2012-09-03 14:45 ` Richard Genoud
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=1345733153.2848.244.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.genoud@gmail.com \
--cc=shmulik.ladkani@gmail.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 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.