From: Jorge Ramirez <jorge.ramirez-ortiz@linaro.org>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: robh@kernel.org, computersforpeace@gmail.com,
dwmw2@infradead.org, matthias.bgg@gmail.com,
linux-mtd@lists.infradead.org, xiaolei.li@mediatek.com,
linux-mediatek@lists.infradead.org, erin.lo@mediatek.com,
blogic@openwrt.org, daniel.thompson@linaro.org
Subject: Re: [PATCH v5 0/2] MTK Smart Device Gen1 NAND Driver
Date: Mon, 20 Jun 2016 10:17:55 -0400 [thread overview]
Message-ID: <5767FB13.5070503@linaro.org> (raw)
In-Reply-To: <20160620135411.2ef381e0@bbrezillon>
On 06/20/2016 07:54 AM, Boris Brezillon wrote:
>> >Tests:
>> >======
>> >
>> >* UBIFS support has been validated on 512MiB device (iozone, dd)
>> >* All drivers/mtd/tests/* pass clean.
>> >* Speed tests:
>> > eraseblock write speed: 7563 KiB/s
>> > eraseblock read speed: 10904 KiB/s
>> > page write speed: 7497 KiB/s
>> > page read speed: 10864 KiB/s
>> > 2 page write speed: 7527 KiB/s
>> > 2 page read speed: 10881 KiB/s
>> > erase speed: 103157 KiB/s
>> > 2x multi-block erase speed: 357445 KiB/s
>> > 4x multi-block erase speed: 362944 KiB/s
>> > 8x multi-block erase speed: 363805 KiB/s
>> > 16x multi-block erase speed: 364237 KiB/s
>> > 32x multi-block erase speed: 364670 KiB/s
>> > 64x multi-block erase speed: 365104 KiB/s
> Applied after fixing a few coding style issues.
>
Awesome.
Thanks for all the reviews and these additional fixes!
jorge
prev parent reply other threads:[~2016-06-20 14:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 15:50 [PATCH v5 0/2] MTK Smart Device Gen1 NAND Driver Jorge Ramirez-Ortiz
2016-06-14 15:50 ` [PATCH v5 1/2] mtd: mediatek: device tree bindings for MTK Jorge Ramirez-Ortiz
2016-06-14 15:50 ` [PATCH v5 2/2] mtd: mediatek: driver for MTK Smart Device Jorge Ramirez-Ortiz
2016-06-14 16:44 ` Boris Brezillon
2016-06-14 17:35 ` Jorge Ramirez
2016-06-20 11:54 ` [PATCH v5 0/2] MTK Smart Device Gen1 NAND Driver Boris Brezillon
2016-06-20 14:17 ` Jorge Ramirez [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=5767FB13.5070503@linaro.org \
--to=jorge.ramirez-ortiz@linaro.org \
--cc=blogic@openwrt.org \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=daniel.thompson@linaro.org \
--cc=dwmw2@infradead.org \
--cc=erin.lo@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=xiaolei.li@mediatek.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;
as well as URLs for NNTP newsgroup(s).