public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] fs/fs.c: do_fsload: measure throughput
Date: Wed, 14 Nov 2012 13:59:49 +0100	[thread overview]
Message-ID: <20121114135949.44e42796@wker> (raw)
In-Reply-To: <1351597766-30442-1-git-send-email-andreas.devel@googlemail.com>

Hi,

On Tue, 30 Oct 2012 12:49:26 +0100
Andreas Bie?mann <andreas.devel@googlemail.com> wrote:

> This patch adds time measurement and throughput calculation for all supported
> fsload commands.
> 
> The output of ext2load changes from
> 
> ---8<---
> 1830666 bytes read
> --->8---
> 
> to
> 
> ---8<---
> 1830666 bytes read in 237 ms (7.4 MiB/s)
> --->8---
> 
> Signed-off-by: Andreas Bie?mann <andreas.devel@googlemail.com>
> ---
> since v1:
>  * use 'time' instead of 'time_start' as suggested by Wolfgang
> 
> since v2:
>  * rebase on top of 045fa1e1142552799ad3203e9e0bc22a11e866ea
>    Now there is some more overhead in the measurement caused by the respective
>    fs-type functions (detect fs-type, eventually do mount and so on).
>    Nevertheless I think such a measurement is good for further improvements
>    like increasing throughput by whatever measures.
> 
>  fs/fs.c |   11 ++++++++++-
>  1 file changed, 10 insertions(+), 1 deletion(-)

Applied to staging/agust at denx.de after rebasing. Also slightly revised
commit log. Thanks!

Anatolij

      parent reply	other threads:[~2012-11-14 12:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17  9:58 [U-Boot] [PATCH] common/cmd_ext_common: measure throughput Andreas Bießmann
2012-10-17 10:05 ` Wolfgang Denk
2012-10-17 10:16   ` Andreas Bießmann
2012-10-25 19:03     ` Tom Rini
2012-10-26  8:20 ` [U-Boot] [PATCH v2] " Andreas Bießmann
2012-10-30 11:49   ` [U-Boot] [PATCH v3] fs/fs.c: do_fsload: " Andreas Bießmann
2012-10-31  7:39     ` Andreas Bießmann
2012-11-04 18:00       ` Tom Rini
2012-11-14 12:59     ` Anatolij Gustschin [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=20121114135949.44e42796@wker \
    --to=agust@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