From: "Dipl.-Ing. Michael Niederle" <mniederle@gmx.at>
To: Chris Mason <chris.mason@oracle.com>
Cc: Zhu Yanhai <zhu.yanhai@gmail.com>,
linux-btrfs@vger.kernel.org, Yan Zheng <zheng.yan@oracle.com>,
austin.zhang@intel.com, yong.y.wang@intel.com,
bing.wei.liu@intel.com, Zhu Yanhai <yanhai.zhu@linux.intel.com>
Subject: Re: What's the benefit of COW without checksum?
Date: Wed, 27 Jan 2010 00:44:29 +0100 [thread overview]
Message-ID: <20100127004429.01516fbd@simplux> (raw)
In-Reply-To: <20100126190705.GB2770@think>
I'm using btrfs for a distribution specialized to be used with USB pen drives.
btrfs ist the first file system (besides nilfs) that is fast enough to be used
with media (flash memory) that has a severe restriction on the number of writes
per second (to be more precise: the number of page deletes per second).
Until now I had to use a layered approached using some kind of union file
system and a ramdisk as the top level layer.
I first testet btrfs last June when it entered the official kernel. At
that time is was much to slow to be used in the described scenario. But the
speedups during the last months made its use possible! :-)
So lots of thanks to Chris Mason and all others who brought us such a
groundbreaking file system. They have done a great piece of work. Yet there's
still a lot to be done, but I'm optimistic that we will end up with a very well
designed file system useable for lots of different application scenarios.
Greetings, Michael
next prev parent reply other threads:[~2010-01-26 23:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <977a2be21001252315w36afcb39v4ba130f6d8e53707@mail.gmail.com>
2010-01-26 19:07 ` What's the benefit of COW without checksum? Chris Mason
2010-01-26 23:44 ` Dipl.-Ing. Michael Niederle [this message]
2010-01-26 7:44 Zhu Yanhai
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=20100127004429.01516fbd@simplux \
--to=mniederle@gmx.at \
--cc=austin.zhang@intel.com \
--cc=bing.wei.liu@intel.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=yanhai.zhu@linux.intel.com \
--cc=yong.y.wang@intel.com \
--cc=zheng.yan@oracle.com \
--cc=zhu.yanhai@gmail.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