From: Artem Bityutskiy <dedekind1@gmail.com>
To: Bhavesh Parekh <bhaveshparekh1@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Perf issue with UBIFS
Date: Tue, 08 Mar 2011 14:31:04 +0200 [thread overview]
Message-ID: <1299587464.2754.27.camel@localhost> (raw)
In-Reply-To: <AANLkTin4FHcpvhsQJkU7pOUPk3-gV+N+1cb0W6_3KC8P@mail.gmail.com>
On Mon, 2011-03-07 at 15:54 +0530, Bhavesh Parekh wrote:
> Hi all,
> I am facing performance issue wil using the UBIFS on our platform.
>
> Kernel version 2.6.36
> Nand device info : Micron chip with 2K page size & 128K erase-size
> ECC : ECC is done by the NAnd-controller.
>
> We have YAFFS2 working on our platform and recently tried UBIFS on our
> platform. YAFF2 Perf is 18MB/s and UBIFS is 11.2 MB/s.
Compression was disabled I guess?
Are you talking about read speed, right?
> Looking at the
> driver log we found that the UBIFS access pattern to the device is
> 4096+48 byte read in the main area, which means that there are lots of
> unaligned read.
Yeah, this is data (uncompressed) + data node header.
> Our platform only support aligned read, so we did an
> optimization by simplying storing the last read page in the buffer
> hopping that on the next read we will be reading the same page and
> gain the perf. Doing this we were able to increase the perf to 14.5
> MB/s
I think this is standard optimization in nand_base.c.
Did you try to enable bulk read by mounting UBIFS with "bulk_read" mount
options (-o bulk_read) ?
> Is there any way we can make UBI to have the access in the aligned way
> only ?
I do not think so. UBIFS has compression, so data node size varies, so
it fundamentally cannot be block-based. YAFFS2 has not compression, thus
it is organized a bit different and it is more "block size aligned",
because YAFFS2 knows that 4KiB of data always take 4KiB on the flash. In
case of UBIFS 4KiB of data may take only 1.5KiB on the flash.
> Other wise perf will be lesser than YAFFS2.
>
> Further we twick the nand-driver and implemented the page-cache mode
> support in the driver.
Yeah, that'd be cool.
> And change the mtd->writesize to 16K so that
> request from the upper layer comes in 16K. It work fine with the
> YAFFS2 and we see a perf gain of 3-4MB/s but UBIFS request pattern
> remains same 4K +48 byte. Is there anything we can do here so that
> UBIFS respect mtd->writesize
Yeah, you can try to do this.
But please, try UBIFS bulk_read option, does it make any difference for
you?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-03-08 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 10:24 Perf issue with UBIFS Bhavesh Parekh
2011-03-08 12:31 ` Artem Bityutskiy [this message]
2011-03-09 12:51 ` Artem Bityutskiy
[not found] ` <AANLkTik_-ZAau27j+7r5EbGyNiPPCH_9a0o9M_H9fsXb@mail.gmail.com>
2011-03-10 13:34 ` Artem Bityutskiy
[not found] ` <AANLkTik9KDEkVT59CqyMM2NUFeBAiAcN_WrnRLqbzaOD@mail.gmail.com>
2011-03-31 12:10 ` 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=1299587464.2754.27.camel@localhost \
--to=dedekind1@gmail.com \
--cc=bhaveshparekh1@gmail.com \
--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