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: Thu, 31 Mar 2011 15:10:44 +0300 [thread overview]
Message-ID: <1301573444.2828.52.camel@localhost> (raw)
In-Reply-To: <AANLkTik9KDEkVT59CqyMM2NUFeBAiAcN_WrnRLqbzaOD@mail.gmail.com>
On Thu, 2011-03-17 at 15:14 +0530, Bhavesh Parekh wrote:
> Thanks Artem.
> Patches you mention helped alot. Now the perf is almost same as that
> of YAFFS2.
>
> I think there will be changes require in the root-fs creation
> tool(ubinize) as well to support the writebufsize. Correct ?
No, I do not think so.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2011-03-31 12:13 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
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 [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=1301573444.2828.52.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