public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Corentin Chary <corentincj@iksaif.net>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] UBI: Decrease I/O count in ubi_scan
Date: Tue, 21 Jul 2009 15:14:11 +0300	[thread overview]
Message-ID: <1248178451.24676.9.camel@localhost> (raw)
In-Reply-To: <1248175591-4592-1-git-send-email-corentincj@iksaif.net>

On Tue, 2009-07-21 at 13:26 +0200, Corentin Chary wrote:
> Merge ec_hdr and vid_hdr read in one ubi_io_read()
> This result in a 25% speedup with nandsim, and 6%
> speedup on an AT91SAM9263 board with a 200Mo UBI volume.
> 
> Signed-off-by: Corentin Chary <corentincj@iksaif.net>
> ---
>  drivers/mtd/ubi/io.c   |   67 ++++++++++++++++++++++++++++++++++++++++++++++-
>  drivers/mtd/ubi/scan.c |   35 +++++++++++++------------
>  drivers/mtd/ubi/ubi.h  |    4 +++
>  3 files changed, 87 insertions(+), 19 deletions(-)

Yeah, I did the same optimization some time ago:

http://lists.infradead.org/pipermail/linux-mtd/2008-April/021311.html

Could you please take a look at those patches as well, and if they
are any better, use them or improve yours. I do not remember the
details, to be frank.

No one reported a significant improvement, so I dropped it.
nandsim improvement is not very interesting, but the AT91SAM9263 is.
Which flash is there? And why do you presume is the improvement -
just less calls to MTD or really less I/O? Note MTD usually caches
the last read NAND page, so usually this is not about less I/O.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

  reply	other threads:[~2009-07-21 12:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 11:26 [PATCH] UBI: Decrease I/O count in ubi_scan Corentin Chary
2009-07-21 12:14 ` Artem Bityutskiy [this message]
2009-07-21 13:42   ` Corentin Chary
2009-07-21 14:15     ` Artem Bityutskiy
2009-07-21 14:22       ` Corentin Chary
2009-07-22  8:51       ` Corentin Chary
2009-07-22  8:55         ` Artem Bityutskiy

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=1248178451.24676.9.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=corentincj@iksaif.net \
    --cc=linux-mtd@lists.infradead.org \
    /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