From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Hunter Adrian (Nokia-MS/Helsinki)" <adrian.hunter@nokia.com>,
linux-mtd <linux-mtd@lists.infradead.org>
Cc: Bhavesh Parekh <bhaveshparekh1@gmail.com>
Subject: UBIFS defaults?
Date: Wed, 09 Mar 2011 15:01:27 +0200 [thread overview]
Message-ID: <1299675687.2741.14.camel@localhost> (raw)
Hi,
currently, UBIFS checks data CRC on read by default, i.e., the
'chk_data_crc' mount option is the default one. This makes people who
apply benchmarks less happy, because they just use the defaults.
Should we make the 'no_chk_data_crc' mount option to be the default
instead? The rationale is that people who do care to read the
documentation can switch to 'chk_data_crc' if they need, and people who
do quick UBIFS evaluation will end up with faster read speed by default.
See this section for more information about the 'no_chk_data_crc' mount
option: http://www.linux-mtd.infradead.org/doc/ubifs.html#L_checksumming
Would be nice to hear UBIFS users' opinion.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next reply other threads:[~2011-03-09 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 13:01 Artem Bityutskiy [this message]
2011-03-10 7:04 ` UBIFS defaults? Artem Bityutskiy
2011-03-10 8:48 ` Jon Povey
2011-03-10 14:28 ` 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=1299675687.2741.14.camel@localhost \
--to=dedekind1@gmail.com \
--cc=adrian.hunter@nokia.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