From: "Jörn Engel" <joern@logfs.org>
To: Jamie Lokier <jamie@shareable.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: big flash disks?
Date: Mon, 2 Jun 2008 13:55:38 +0200 [thread overview]
Message-ID: <20080602115538.GC21359@logfs.org> (raw)
In-Reply-To: <20080602104330.GD31032@shareable.org>
On Mon, 2 June 2008 11:43:30 +0100, Jamie Lokier wrote:
>
> I'm surprised.
> What sort of format change does SSD require, relative to NOR/NAND flash?
Flash allows one to do partial writes to blocks. SSDs generally don't.
Logfs currently does partial writes for atomic transactions, to make
creat(), unlink(), rename() and friends behave well. Depending on your
SSD a simple creat() can blow up to writing several megabytes on the
actual medium.
I never claimed to actually like those suckers. ;)
> For SSD I would like to see a filesystem that combines the best
> characteristics of btrfs and logfs - the are enough similarities
> between them.
True. Right now I think it is a better idea to keep the two seperate.
But in the future a combination would be rather useful.
Jörn
--
Fantasy is more important than knowledge. Knowledge is limited,
while fantasy embraces the whole world.
-- Albert Einstein
next prev parent reply other threads:[~2008-06-02 11:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 18:42 big flash disks? Jamie Lokier
2008-06-01 20:41 ` Josh Boyer
2008-06-02 5:59 ` Artem Bityutskiy
2008-06-02 8:23 ` Jörn Engel
2008-06-02 10:43 ` Jamie Lokier
2008-06-02 11:55 ` Jörn Engel [this message]
2008-06-02 12:32 ` Jamie Lokier
2008-06-03 18:09 ` Jörn Engel
2008-06-03 18:44 ` Jamie Lokier
2008-06-04 6:25 ` Jörn Engel
2008-06-02 7:28 ` Jörn Engel
2008-06-02 10:41 ` Jamie Lokier
2008-06-02 11:43 ` Jörn Engel
2008-06-02 12:48 ` Jamie Lokier
2008-06-03 18:12 ` Jörn Engel
2008-06-03 18:56 ` Jamie Lokier
2008-06-04 6:18 ` Jörn Engel
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=20080602115538.GC21359@logfs.org \
--to=joern@logfs.org \
--cc=jamie@shareable.org \
--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