From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
To: "richard.weinberger@gmail.com" <richard.weinberger@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: xxhash ?
Date: Thu, 28 Dec 2017 09:44:05 +0000 [thread overview]
Message-ID: <1514454242.5843.4.camel@infinera.com> (raw)
In-Reply-To: <CAFLxGvyDWQCwUpGcn+9ZbSXKxfXpMBT5WpCjA5NZ1GR+ueSUVQ@mail.gmail.com>
On Thu, 2017-12-28 at 10:38 +0100, Richard Weinberger wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>
> Joakim,
>
> On Thu, Dec 28, 2017 at 7:13 AM, Joakim Tjernlund
> <Joakim.Tjernlund@infinera.com> wrote:
> > Now that xxhash is in the tree one could look at replacing
> > crc32 in JFFS2/UBI. This would make checksumming much faster.
>
> Since this will require a change of the on-disk format we have to be
> very careful.
> Do you have a use-case where crc32 is the bottle neck?
Not directly, I remember the good old days when mounting took forever, mostly
due to crc32. I then optimized crc32(the big tables you have today) and some
other JFFS2 optimizations. Since crc32 is used everywhere in JFFS2 I figure
xxhash would help, especially on low end CPUs
Jocke
next prev parent reply other threads:[~2017-12-28 9:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 6:13 xxhash ? Joakim Tjernlund
2017-12-28 9:38 ` Richard Weinberger
2017-12-28 9:44 ` Joakim Tjernlund [this message]
2017-12-28 10:06 ` Richard Weinberger
2017-12-28 10:52 ` Joakim Tjernlund
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=1514454242.5843.4.camel@infinera.com \
--to=joakim.tjernlund@infinera.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@gmail.com \
/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