From: Artem Bityutskiy <dedekind@infradead.org>
To: dsaxena@plexity.net
Cc: linux-mtd@lists.infradead.org
Subject: Re: Understanding UBIFS flash overhead
Date: Mon, 13 Oct 2008 10:45:22 +0300 [thread overview]
Message-ID: <1223883922.3395.62.camel@sauron> (raw)
In-Reply-To: <20081010210036.GA12173@trantor.hsd1.or.comcast.net>
On Fri, 2008-10-10 at 14:00 -0700, Deepak Saxena wrote:
> I'm working on getting UBIFS going on the OLPC XO and am trying to
> understand what I am seeing in regards to file system size.
BTW, consider to try new "bulk_read" mount option which may improve file
read speed. The "no_chk_data_crc" might be considered as well.
We'd be interested to get some digits from you to see whether
"bulk_read" improves things for you. Please, read here:
http://marc.info/?l=linux-kernel&m=122276053307842&w=2
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-10-13 7:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 21:00 Understanding UBIFS flash overhead Deepak Saxena
2008-10-13 6:48 ` Artem Bityutskiy
2008-10-14 22:56 ` Deepak Saxena
2008-10-15 12:59 ` Artem Bityutskiy
2008-10-13 7:45 ` Artem Bityutskiy [this message]
2008-10-14 22:56 ` Deepak Saxena
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=1223883922.3395.62.camel@sauron \
--to=dedekind@infradead.org \
--cc=dsaxena@plexity.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