From: Charles Manning <manningc2@actrix.gen.nz>
To: linux-mtd@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Huge ubi or ubifs sync slowdown since 2.6.32
Date: Tue, 21 Dec 2010 11:36:22 +1300 [thread overview]
Message-ID: <201012211136.22254.manningc2@actrix.gen.nz> (raw)
Hi All
I've been looking into a ubifs performance regression on linux-omap 2.6.37.
My test is pretty simple, copy a 2Mbyte file and sync.
# sync; date; cp 2Mbyte-file foo; sync; date
On 2.6.32 and earler, the time between the two dates was around 3 seconds.
On linux-omap master it is around 14 seconds. Ouch!
At first I thought the problem was due to changes in the OMAP nand drivers,
but raw randwrite speed is actually a bit faster. This suggest the finger
should be pointed at ubi or ubifs.
I then thought that perhaps the layout of my ubinized image might be a
contributing factor so I erased the partition, ubiformatted and ubimkvoled.
The problem persisted,
Any suggestions as to what might be broken or how to debug this deeper?
Thanks
Charles
next reply other threads:[~2010-12-20 22:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 22:36 Charles Manning [this message]
2010-12-22 14:43 ` Huge ubi or ubifs sync slowdown since 2.6.32 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=201012211136.22254.manningc2@actrix.gen.nz \
--to=manningc2@actrix.gen.nz \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.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