From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 5/5] fastboot: sparse: improve CHUNK_TYPE_FILL write performance
Date: Wed, 22 Jun 2016 21:39:42 +0200 [thread overview]
Message-ID: <20160622193942.GZ26668@lukather> (raw)
In-Reply-To: <CAM7GXonNVWv02cAEtYM7TZLFn-RkLOb9YXkhWja5ZYn-S8SvZQ@mail.gmail.com>
On Thu, Jun 16, 2016 at 10:34:37AM -0700, Steve Rae wrote:
> On Wed, Jun 15, 2016 at 1:36 AM, Maxime Ripard
> <maxime.ripard@free-electrons.com> wrote:
> > On Tue, Jun 07, 2016 at 11:19:39AM -0700, Steve Rae wrote:
> >> - increase the size of the fill buffer
> >> - testing has shown a 10x improvement when the sparse image
> >> has large CHUNK_TYPE_FILL chunks
> >>
> >> Signed-off-by: Steve Rae <srae@broadcom.com>
> >> ---
> >>
> >> Changes in v2: None
> >>
> >> common/image-sparse.c | 37 +++++++++++++++++++++++++++----------
> >> 1 file changed, 27 insertions(+), 10 deletions(-)
> >>
> >> diff --git a/common/image-sparse.c b/common/image-sparse.c
> >> index 9632c6f..ddf5772 100644
> >> --- a/common/image-sparse.c
> >> +++ b/common/image-sparse.c
> >> @@ -1,4 +1,3 @@
> >> -
> >> /*
> >> * Copyright (c) 2009, Google Inc.
> >> * All rights reserved.
> >> @@ -46,6 +45,10 @@
> >>
> >> #include <linux/math64.h>
> >>
> >> +#ifndef CONFIG_FASTBOOT_FLASH_FILLBUF_SIZE
> >> +#define CONFIG_FASTBOOT_FLASH_FILLBUF_SIZE (1024 * 512)
> >
> > I wonder whether that would be better to just put the number of blocks
> > there.
>
> I wanted to imply that this is not just a random value (even though
> the code does values which are not a multiple of the info->blksz)
I know, but what I was saying is that NAND block size are usually a
couple of kilobytes, while the benefit here probably comes from the
number of blocks, not the actual size they take, which, for the same
benefits, will probably be the same number of blocks, but implies a
bigger size.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160622/2779844c/attachment.sig>
next prev parent reply other threads:[~2016-06-22 19:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 18:19 [U-Boot] [PATCH v2 0/5] Update fastboot sparse image handling Steve Rae
2016-06-07 18:19 ` [U-Boot] [PATCH v2 1/5] fastboot: sparse: remove session-id logic Steve Rae
2016-06-28 1:12 ` [U-Boot] [U-Boot, v2, " Tom Rini
2016-06-07 18:19 ` [U-Boot] [PATCH v2 2/5] fastboot: sparse: resync common/image-sparse.c (part 1) Steve Rae
2016-06-15 8:18 ` Maxime Ripard
2016-06-16 17:29 ` Steve Rae
2016-06-22 19:36 ` Maxime Ripard
2016-06-22 21:44 ` Tom Rini
2016-06-28 1:12 ` [U-Boot] [U-Boot, v2, " Tom Rini
2016-06-07 18:19 ` [U-Boot] [PATCH v2 3/5] fastboot: sparse: resync common/image-sparse.c (part 2) Steve Rae
2016-06-28 1:12 ` [U-Boot] [U-Boot, v2, " Tom Rini
2016-06-07 18:19 ` [U-Boot] [PATCH v2 4/5] fastboot: sparse: implement reserve() Steve Rae
2016-06-15 8:31 ` Maxime Ripard
2016-06-28 1:12 ` [U-Boot] [U-Boot,v2,4/5] " Tom Rini
2016-06-07 18:19 ` [U-Boot] [PATCH v2 5/5] fastboot: sparse: improve CHUNK_TYPE_FILL write performance Steve Rae
2016-06-15 8:36 ` Maxime Ripard
2016-06-16 17:34 ` Steve Rae
2016-06-16 17:47 ` Steve Rae
2016-06-22 19:39 ` Maxime Ripard [this message]
2016-06-28 1:12 ` [U-Boot] [U-Boot, v2, " Tom Rini
2016-06-07 18:36 ` [U-Boot] [PATCH v2 0/5] Update fastboot sparse image handling Sergey Kubushyn
2016-06-07 18:38 ` Steve Rae
2016-06-07 20:20 ` Steve Rae
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=20160622193942.GZ26668@lukather \
--to=maxime.ripard@free-electrons.com \
--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