From: Tim Riker <Tim@Rikers.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: mtd <linux-mtd@lists.infradead.org>, jffs-dev <jffs-dev@axis.com>
Subject: Re: Wear Leveling in JFFS2 NOT working!(?)
Date: Mon, 30 Apr 2001 19:24:55 -0600 [thread overview]
Message-ID: <3AEE1067.599A8ACF@Rikers.org> (raw)
In-Reply-To: Pine.LNX.4.33.0104302356320.10289-100000@imladris.demon.co.uk
David Woodhouse wrote:
> Either:
> 1. After scan, move the first <n> blocks in the list to the end
> of the list, where 1 < n < sizeof(list).
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.
> 2. When adding entries to the lists during scan, do something
> like: if (jiffies % 1) list_add_tail() else list_add().
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.
--
Tim Riker - http://rikers.org/ - short SIGs! <g>
All I need to know I could have learned in Kindergarten
... if I'd just been paying attention.
next prev parent reply other threads:[~2001-05-01 1:25 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 [this message]
2001-05-01 7:21 ` David Woodhouse
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=3AEE1067.599A8ACF@Rikers.org \
--to=tim@rikers.org \
--cc=dwmw2@infradead.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 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.