public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Tim Riker <Tim@Rikers.org>
Cc: mtd <linux-mtd@lists.infradead.org>, jffs-dev <jffs-dev@axis.com>
Subject: Re: Wear Leveling in JFFS2 NOT working!(?)
Date: Tue, 01 May 2001 13:35:29 +0100	[thread overview]
Message-ID: <3890.988720529@redhat.com> (raw)
In-Reply-To: <3AEE6920.89563C1B@Rikers.org>

Tim@Rikers.org said:
> > The 'jiffies mod' trick would give repeatable results.

> RTC should not be relied on as some hardware has this broken (iPAQ at
> present ;-) What about totaling the checksums for each block as we
> scan them at mount time and then mod that by numblocks? This would
> also be repeatable given the same original filesystem.

By 'repeatable' I meant it would give a badly-distributed pattern, which is
a bad thing. It's not at all necessary that it's predictable given the 
filesystem state before mount.

Totalling the checksums as you suggest would work, but I'm a little 
reluctant to do that because of the layering implications. It would be 
nicer if we could use information which is already available to the code at 
that point. How about just rotating the lists by (highest_inode + 
highest_version_in_it) ?

Over the lifetime of the filesystem, the range of 
	(highest_inode + highest_ver) % nr_blocks
is going to be fairly evenly distributed, isn't it?

--
dwmw2

  reply	other threads:[~2001-05-01 12:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-30 22:26 Wear Leveling in JFFS2 NOT working!(?) Vipin Malik
2001-04-30 23:06 ` David Woodhouse
2001-05-01  1:24   ` Tim Riker
2001-05-01  7:21     ` David Woodhouse
2001-05-01  7:43       ` Tim Riker
2001-05-01 12:35         ` David Woodhouse [this message]
2001-05-01 11:55       ` Jim Gettys
2001-05-01 12:29         ` David Woodhouse
2001-05-03 15:27   ` Vipin Malik
2001-05-03 15:29     ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2001-05-03 15:51 Chris Read
2001-05-03 16:09 ` David Woodhouse

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=3890.988720529@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=Tim@Rikers.org \
    --cc=jffs-dev@axis.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