From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: "Antoine Tenart" <antoine.tenart@free-electrons.com>,
zmxu@marvell.com, jszhang@marvell.com,
"Boris Brezillon" <boris.brezillon@free-electrons.com>,
"David Woodhouse" <dwmw2@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Ezequiel Garcia" <ezequiel.garcia@free-electrons.com>,
"Gregory Clément" <gregory.clement@free-electrons.com>,
"Brian Norris" <computersforpeace@gmail.com>,
"Robert Jarzmik" <robert.jarzmik@free.fr>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH v4 0/5] mtd: pxa3xx_nand: rework the timing setup
Date: Thu, 22 Oct 2015 17:42:44 +0200 [thread overview]
Message-ID: <20151022174244.61eaf79e@free-electrons.com> (raw)
In-Reply-To: <CAAEAJfCmo5u6=5GN6+k8GsFhC0dg477gVYY+t77uODP-PgWLGw@mail.gmail.com>
Dear Ezequiel Garcia,
On Thu, 22 Oct 2015 12:22:24 -0300, Ezequiel Garcia wrote:
> Could you compare NAND throughput using keep-config (keeping
> the bootloader timings) and without keep-config (with ONFI timings) ?
Seems like we are within the measurement noise. I did each test only
once, and the test lasts only a few seconds, but here are the results:
Without keep-config (i.e ONFI timings) :
# time dd if=/dev/mtd3 of=/dev/null bs=1M
32+0 records in
32+0 records out
real 0m 3.54s
user 0m 0.00s
sys 0m 0.26s
With keep-config (i.e bootloader timings)
# time dd if=/dev/mtd3 of=/dev/null bs=1M
32+0 records in
32+0 records out
real 0m 3.77s
user 0m 0.00s
sys 0m 0.21s
I.e we are apparently slightly faster with the ONFI timings. However
again, the test duration is very short, and I didn't repeat the test
several times.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/5] mtd: pxa3xx_nand: rework the timing setup
Date: Thu, 22 Oct 2015 17:42:44 +0200 [thread overview]
Message-ID: <20151022174244.61eaf79e@free-electrons.com> (raw)
In-Reply-To: <CAAEAJfCmo5u6=5GN6+k8GsFhC0dg477gVYY+t77uODP-PgWLGw@mail.gmail.com>
Dear Ezequiel Garcia,
On Thu, 22 Oct 2015 12:22:24 -0300, Ezequiel Garcia wrote:
> Could you compare NAND throughput using keep-config (keeping
> the bootloader timings) and without keep-config (with ONFI timings) ?
Seems like we are within the measurement noise. I did each test only
once, and the test lasts only a few seconds, but here are the results:
Without keep-config (i.e ONFI timings) :
# time dd if=/dev/mtd3 of=/dev/null bs=1M
32+0 records in
32+0 records out
real 0m 3.54s
user 0m 0.00s
sys 0m 0.26s
With keep-config (i.e bootloader timings)
# time dd if=/dev/mtd3 of=/dev/null bs=1M
32+0 records in
32+0 records out
real 0m 3.77s
user 0m 0.00s
sys 0m 0.21s
I.e we are apparently slightly faster with the ONFI timings. However
again, the test duration is very short, and I didn't repeat the test
several times.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-10-22 15:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 8:28 [PATCH v4 0/5] mtd: pxa3xx_nand: rework the timing setup Antoine Tenart
2015-10-21 8:28 ` Antoine Tenart
2015-10-21 8:29 ` [PATCH v4 1/5] mtd: pxa3xx: prepare allowing compile test Antoine Tenart
2015-10-21 8:29 ` Antoine Tenart
2015-10-21 8:29 ` [PATCH v4 2/5] mtd: nand: allow compile test of MTD_NAND_PXA3xx Antoine Tenart
2015-10-21 8:29 ` Antoine Tenart
2015-10-26 18:34 ` Brian Norris
2015-10-26 18:34 ` Brian Norris
2015-10-21 8:29 ` [PATCH v4 3/5] mtd: pxa3xx_nand: add helpers to setup the timings Antoine Tenart
2015-10-21 8:29 ` Antoine Tenart
2015-10-21 8:29 ` [PATCH v4 4/5] mtd: pxa3xx_nand: rework flash detection and timing setup Antoine Tenart
2015-10-21 8:29 ` Antoine Tenart
2015-10-21 8:29 ` [PATCH v4 5/5] mtd: pxa3xx_nand: clean up the pxa3xx timings Antoine Tenart
2015-10-21 8:29 ` Antoine Tenart
2015-10-22 15:12 ` [PATCH v4 0/5] mtd: pxa3xx_nand: rework the timing setup Thomas Petazzoni
2015-10-22 15:12 ` Thomas Petazzoni
2015-10-22 15:22 ` Ezequiel Garcia
2015-10-22 15:22 ` Ezequiel Garcia
2015-10-22 15:42 ` Thomas Petazzoni [this message]
2015-10-22 15:42 ` Thomas Petazzoni
2015-11-02 15:49 ` Ezequiel Garcia
2015-11-02 15:49 ` Ezequiel Garcia
2015-10-25 20:53 ` Robert Jarzmik
2015-10-25 20:53 ` Robert Jarzmik
2015-10-26 13:50 ` Ezequiel Garcia
2015-10-26 13:50 ` Ezequiel Garcia
2015-10-26 18:38 ` Brian Norris
2015-10-26 18:38 ` Brian Norris
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=20151022174244.61eaf79e@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=antoine.tenart@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=gregory.clement@free-electrons.com \
--cc=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=robert.jarzmik@free.fr \
--cc=sebastian.hesselbarth@gmail.com \
--cc=zmxu@marvell.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.