From: Artem Bityutskiy <dedekind1@gmail.com>
To: Charles Manning <manningc2@actrix.gen.nz>
Cc: linux-omap@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: Huge ubi or ubifs sync slowdown since 2.6.32
Date: Wed, 22 Dec 2010 16:43:12 +0200 [thread overview]
Message-ID: <1293028992.12773.18.camel@localhost> (raw)
In-Reply-To: <201012211136.22254.manningc2@actrix.gen.nz>
On Tue, 2010-12-21 at 11:36 +1300, Charles Manning wrote:
> 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?
Can you try this on nandsim and see if there are still differences? You
can make nandsim slower by injecting an udelay somewhere. Try this on
your x86 host - this way you'll narrow this down to an OMAP-specific or
platform-independent problem.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-12-22 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 22:36 Huge ubi or ubifs sync slowdown since 2.6.32 Charles Manning
2010-12-22 14:43 ` Artem Bityutskiy [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=1293028992.12773.18.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=manningc2@actrix.gen.nz \
/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