From: Amit Kumar Sharma <amitsharma.9@samsung.com>
To: Adrian Hunter <adrian.hunter@nokia.com>,
"Korhonen Mika.2 (EXT-Ardites/Oulu)"
<ext-mika.2.korhonen@nokia.com>
Cc: amul.saha@samsung.com,
"Bityutskiy Artem \(Nokia-D/Helsinki\)"
<Artem.Bityutskiy@nokia.com>,
kyungmin.park@samsung.com, linux-mtd@lists.infradead.org
Subject: Re: [PATCH v5 2/3] MTD: OneNAND: multiblock erase support
Date: Fri, 23 Oct 2009 14:03:02 +0530 [thread overview]
Message-ID: <3AF129BF059348D6B4912F6DB21DA9B2@sisodomain.com> (raw)
In-Reply-To: 4AE164AE.80304@nokia.com
> Korhonen Mika.2 (EXT-Ardites/Oulu) wrote:
>> ext Amit Kumar Sharma wrote:
>>> Hi Mika,
>>>
>>> Do you have any use case for using multiblock erase.
>>>
>>>
>>> Thanks
>>> Amit
>>>
>> Yes, e.g. during development/loop testing we need to
>> flash a new system on an MTD partition.
>> The (UBIFS) system could be tiny but the partition large
>> in which case the erase time becomes even more
>> significant.
>> Even in more usual cases of reflashing a bigger system
>> this gives ca. 5 % speed improvement.
>>
>> Mika
>>
>
> However the API is imperfect because AFAICT OneNAND
> multiblock erase
> does not require that the blocks are sequential i.e. any
> 64 eraseblocks
> from the same chip can be erased together. So we would
> really need an
> 'erasev()' API to take complete advantage of it.
>
I feel we should have a use case for multi block erase for
UBI wear leveling.
it is just a opinion.
Multi block erase can be useful if implement 'erasev' api
at file system level.
Thanks
Amit
next prev parent reply other threads:[~2009-10-23 8:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 9:52 [PATCH v5 0/3] MTD: OneNAND: multiblock erase support Mika Korhonen
2009-10-12 9:52 ` [PATCH v5 1/3] MTD: OneNAND: move erase method to a separate function Mika Korhonen
2009-10-12 9:52 ` [PATCH v5 2/3] MTD: OneNAND: multiblock erase support Mika Korhonen
2009-10-12 9:52 ` [PATCH v5 3/3] MTD: OneNAND: fix double printing of function name Mika Korhonen
2009-10-20 13:09 ` [PATCH v5 2/3] MTD: OneNAND: multiblock erase support Adrian Hunter
2009-10-23 4:34 ` Artem Bityutskiy
2009-10-23 5:19 ` Mika Korhonen
2009-10-23 5:22 ` Artem Bityutskiy
2009-10-23 5:41 ` Amit Kumar Sharma
2009-10-23 6:00 ` Artem Bityutskiy
2009-10-23 6:05 ` Mika Korhonen
2009-10-23 8:09 ` Adrian Hunter
2009-10-23 8:33 ` Amit Kumar Sharma [this message]
2009-10-20 8:57 ` [PATCH v5 0/3] " 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=3AF129BF059348D6B4912F6DB21DA9B2@sisodomain.com \
--to=amitsharma.9@samsung.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=adrian.hunter@nokia.com \
--cc=amul.saha@samsung.com \
--cc=ext-mika.2.korhonen@nokia.com \
--cc=kyungmin.park@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox