From: Hans Reiser <reiser@namesys.com>
To: Daniel Egger <degger@fhm.edu>
Cc: Yury Umanets <umka@namesys.com>,
Nikita Danilov <Nikita@Namesys.COM>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
reiserfs mailing list <reiserfs-list@namesys.com>,
Alexander Lyamin <flx@namesys.com>
Subject: Re: Reiser4 status: benchmarked vs. V3 (and ext3)
Date: Mon, 28 Jul 2003 15:30:35 +0400 [thread overview]
Message-ID: <3F25095B.6070607@namesys.com> (raw)
In-Reply-To: <1059315015.10692.207.camel@sonja>
Daniel Egger wrote:
>Are you sure CF cards have wear leveling? I'm pretty confident that they
>have defect sector management but no wear leveling. There's a huge
>difference between those two.
>
I am told that they do by flx. After all, they are most used for the
FAT filesystem.
--
Hans
next prev parent reply other threads:[~2003-07-28 11:17 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 21:02 Reiser4 status: benchmarked vs. V3 (and ext3) Hans Reiser
2003-07-24 4:26 ` Tupshin Harper
2003-07-24 4:31 ` Shawn
2003-07-24 4:56 ` Tupshin Harper
2003-07-24 5:21 ` Shawn
2003-07-24 5:33 ` Shawn
2003-07-24 11:10 ` Nikita Danilov
2003-07-24 15:10 ` Tupshin Harper
2003-07-24 15:26 ` Larry McVoy
2003-07-24 15:32 ` Tupshin Harper
2003-07-24 15:54 ` Larry McVoy
2003-07-24 15:32 ` Shawn
2003-07-27 12:28 ` Hans Reiser
2003-07-27 12:45 ` Tomas Szepe
2003-07-27 14:01 ` Hans Reiser
2003-07-27 15:04 ` Gene Heskett
2003-07-24 15:59 ` Daniel Egger
2003-07-24 17:07 ` Nikita Danilov
2003-07-24 21:10 ` Tupshin Harper
2003-07-25 12:57 ` Nikita Danilov
2003-07-25 0:39 ` Daniel Egger
2003-07-25 13:02 ` Nikita Danilov
2003-07-25 14:20 ` Daniel Egger
2003-07-25 14:39 ` Yury Umanets
2003-07-26 1:08 ` Daniel Egger
2003-07-26 7:19 ` Yury Umanets
2003-07-26 14:13 ` Daniel Egger
2003-07-26 14:54 ` Yury Umanets
2003-07-26 15:21 ` Daniel Egger
2003-07-27 3:28 ` Valdis.Kletnieks
2003-07-27 10:30 ` Yury Umanets
2003-07-27 11:05 ` Daniel Egger
2003-07-27 11:46 ` Yury Umanets
2003-08-08 14:01 ` David Woodhouse
2003-08-08 14:28 ` Bernd Eckenfels
2003-08-08 23:58 ` David Woodhouse
2003-08-09 0:29 ` Bernd Eckenfels
2003-08-09 0:38 ` David Woodhouse
2003-07-27 13:31 ` Hans Reiser
2003-07-27 14:13 ` Yury Umanets
2003-07-27 13:28 ` Hans Reiser
2003-07-27 14:10 ` Daniel Egger
2003-07-27 14:15 ` Yury Umanets
2003-08-13 20:12 ` Bill Davidsen
2003-08-14 5:04 ` Yury Umanets
2003-08-14 14:10 ` David Woodhouse
2003-08-15 11:15 ` Yury Umanets
2003-08-15 15:28 ` Bill Davidsen
2003-08-15 15:53 ` David Woodhouse
2003-08-14 13:58 ` David Woodhouse
2003-07-27 15:30 ` Bernd Eckenfels
2003-07-27 15:49 ` Alan Cox
2003-08-08 13:23 ` David Woodhouse
2003-07-28 11:30 ` Hans Reiser [this message]
2003-07-26 17:14 ` Jussi Laako
2003-07-27 13:35 ` Hans Reiser
2003-08-08 14:08 ` David Woodhouse
2003-07-27 12:59 ` Hans Reiser
2003-07-27 14:16 ` Daniel Egger
2003-07-27 15:32 ` Bernd Eckenfels
2003-08-08 14:29 ` David Woodhouse
2003-07-28 12:44 ` Hans Reiser
2003-07-28 13:06 ` Daniel Egger
2003-07-28 13:29 ` Hans Reiser
2003-07-28 13:48 ` Hans Reiser
2003-07-27 12:38 ` Hans Reiser
2003-07-26 8:33 ` Andrew Morton
2003-07-27 13:24 ` Hans Reiser
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=3F25095B.6070607@namesys.com \
--to=reiser@namesys.com \
--cc=Nikita@Namesys.COM \
--cc=degger@fhm.edu \
--cc=flx@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
--cc=umka@namesys.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