All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: xxhash ?
Date: Thu, 28 Dec 2017 11:06:25 +0100	[thread overview]
Message-ID: <2450093.pHMqlGidjZ@blindfold> (raw)
In-Reply-To: <1514454242.5843.4.camel@infinera.com>

Am Donnerstag, 28. Dezember 2017, 10:44:05 CET schrieb Joakim Tjernlund:
> 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

Unless this gives a decent speedup I don't think we should add new features to 
JFFS2.
For UBI/UBIFS it is a different story. Did you also tests with UBI?

Thanks,
//richard

  reply	other threads:[~2017-12-28 10:06 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
2017-12-28 10:06     ` Richard Weinberger [this message]
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=2450093.pHMqlGidjZ@blindfold \
    --to=richard@nod.at \
    --cc=Joakim.Tjernlund@infinera.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.