From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] spi: sf: add support for throughput mesurement of sf read/write
Date: Fri, 18 Dec 2015 07:07:38 +0100 [thread overview]
Message-ID: <5673A2AA.60204@denx.de> (raw)
In-Reply-To: <CAD6G_RTX_Oj88m8H75Y==qyHGAor2nar1GV3+=FzysS8u856Og@mail.gmail.com>
On 17.12.2015 17:44, Jagan Teki wrote:
> On 17 December 2015 at 13:26, Mugunthan V N <mugunthanvnm@ti.com> wrote:
>> On Thursday 17 December 2015 12:43 PM, Jagan Teki wrote:
>>> On 17 December 2015 at 12:33, Mugunthan V N <mugunthanvnm@ti.com> wrote:
>>>> Jagan
>>>>
>>>> On Tuesday 27 October 2015 07:24 PM, Mugunthan V N wrote:
>>>>> This patch adds time measurement and throughput calculation for
>>>>> sf read/write commands.
>>>>>
>>>>> The output of sf read changes from
>>>>>
>>>>> ---8<---
>>>>> SF: 4096 bytes @ 0x0 Read: OK
>>>>> --->8---
>>>>>
>>>>> to
>>>>>
>>>>> ---8<---
>>>>> SF: 4096 bytes @ 0x0 Read: OK in 6 ms (666 KiB/s)
>>>>> --->8---
>>>>>
>>>>> Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com>
>>>
>>> Was it similar to 'sf update' ? please check it once.
>>>
>>
>> sf update out similar but also uses progressive output, in read/write
>> case it can't be done. The final throughput measurement is similar on
>> both update and read/write.
>
> True, that's what if we need a progressed throughput just use 'sf
> update' else normal 'sf read/write' It's look not good to me to add
> extra code on top of generic commands. What ever we wanted to extend
> features let's added it on 'sf update' than sf read/write, Sorry.
If I need to measure the time of commands, I use the "time"
command ("time sf write ...") by enabling it via CONFIG_CMD_TIME.
This provides all the needed information to detect performance
changes.
Thanks,
Stefan
next prev parent reply other threads:[~2015-12-18 6:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 13:54 [U-Boot] [PATCH] spi: sf: add support for throughput mesurement of sf read/write Mugunthan V N
2015-12-17 7:03 ` Mugunthan V N
2015-12-17 7:13 ` Jagan Teki
2015-12-17 7:56 ` Mugunthan V N
2015-12-17 16:44 ` Jagan Teki
2015-12-18 6:07 ` Stefan Roese [this message]
2015-12-21 5:37 ` Mugunthan V N
2015-12-21 6:00 ` Stefan Roese
2015-12-21 6:07 ` Jagan Teki
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=5673A2AA.60204@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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