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 08:21:16 +0100	[thread overview]
Message-ID: <13672.988701676@redhat.com> (raw)
In-Reply-To: <3AEE1067.599A8ACF@Rikers.org>

Tim@Rikers.org said:
> Providing n is random, this is a good solution. Can the list be hacked
> to change the top/bottom without actually walking through n blocks and
> moving them? I have not looked at the source, but for a linked list
> you could join top and bottom entries and then break n and n-1 nodes
> and start becomes n, end becomes n-1, etc.

Yep, hacking the list is fairly easy. Coming up with a pseudo-random number 
of reasonable quality at boot time when the entropy pool is empty is the 
more interesting bit. The 'jiffies mod' trick would give repeatable
results.

Just to restate the obvious - it doesn't have to be _random_, just evenly 
distributed.

> This will still be somewhat pattern oriented. last blocks scanned will
> be either at front or back so I suspect wear numbers will increase
> towards the end of scanned blocks. ie: first scanned blocks would never
> be on the end of the dirty list.

Agreed.

--
dwmw2

  reply	other threads:[~2001-05-01  7:20 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 [this message]
2001-05-01  7:43       ` Tim Riker
2001-05-01 12:35         ` David Woodhouse
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=13672.988701676@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