From: Artem Bityutskiy <dedekind1@gmail.com>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH 1/2] jffs:2 Move erasing from write_super to GC.
Date: Tue, 16 Feb 2010 13:59:14 +0200 [thread overview]
Message-ID: <1266321554.11659.265.camel@localhost> (raw)
In-Reply-To: <OFFB9662B3.8400DCA7-ONC12576CC.003F62F7-C12576CC.0040EE91@transmode.se>
On Tue, 2010-02-16 at 12:49 +0100, Joakim Tjernlund wrote:
> BTW, I see UBIFS is using CRC16 as well as CRC32. Is there a reason
> you are using CRC16 in UBIFS. Any particular reason for that? CRC16 is
> much slower than crc32 in linux since the CRC32 impl. was optimized
> by yours truly long time ago just because it was impacting mount time
> for JFFS2.
We use crc16 only for LPT (Leb Properties Tree). The tree is very
optimized to be as small as possible, and we protect very short pieces
of data, this is why crc16 was choosed.
Everything else is protected with crc32.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-02-16 12:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 16:03 [PATCH 1/2] jffs:2 Move erasing from write_super to GC Joakim Tjernlund
2010-02-15 16:03 ` [PATCH 2/2] s/jffs2_erase_pending_trigger/jffs2_garbage_collect_trigger/ Joakim Tjernlund
2010-02-16 8:59 ` Artem Bityutskiy
2010-02-16 9:32 ` Joakim Tjernlund
2010-02-16 14:27 ` Joakim Tjernlund
2010-02-17 7:18 ` Artem Bityutskiy
2010-02-17 7:35 ` Joakim Tjernlund
2010-02-17 7:48 ` Artem Bityutskiy
2010-02-17 7:55 ` Joakim Tjernlund
2010-02-17 8:07 ` Artem Bityutskiy
2010-02-17 8:19 ` Joakim Tjernlund
2010-02-16 8:57 ` [PATCH 1/2] jffs:2 Move erasing from write_super to GC Artem Bityutskiy
2010-02-16 9:18 ` Joakim Tjernlund
2010-02-16 9:45 ` Artem Bityutskiy
2010-02-16 11:49 ` Joakim Tjernlund
2010-02-16 11:59 ` 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=1266321554.11659.265.camel@localhost \
--to=dedekind1@gmail.com \
--cc=joakim.tjernlund@transmode.se \
--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