public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Anopolsky <erpo41@gmail.com>
To: Theodore Tso <tytso@mit.edu>
Cc: postrishi <postrishi@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: Porting Zfs features to ext2/3
Date: Sun, 27 Jul 2008 22:15:59 -0600	[thread overview]
Message-ID: <1217218559.28825.12.camel@telesto> (raw)
In-Reply-To: <20080727233855.GB9378@mit.edu>

[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]

On Sun, 2008-07-27 at 19:38 -0400, Theodore Tso wrote:
> On Sun, Jul 27, 2008 at 04:54:41PM -0600, Eric Anopolsky wrote:
> > On Sun, 2008-07-27 at 01:49 -0700, postrishi wrote:
> > > Hello
> > > 
> > > I want to know that has any work been done to port the Zfs features to
> > > ext2/3
> > 
> > Did you know that ZFS is available for Linux?
> 
> ZFS is available in a FUSE filesystem.  As a userspace filesystem, it
> means a huge number of context switches to get data between the disk,
> to the kernel, to the FUSE userspace, back to the kernel, and to the
> process trying to access the ZFS file.  That's not going to be high
> performance.  For someone who wants to migrate from Solaris to Linux,
> it might be useful, but I'm not sure you would really want to use a
> ZFS/FUSE implementation in production.

It's true that ZFS on FUSE performance isn't all it could be right now.
However, ZFS on FUSE is currently not taking advantage of mechanisms
FUSE provides to improve performance. For an example of what can be
achieved, check out http://www.ntfs-3g.org/performance.html .

FWIW, I am satisfied with its performance for backups of my home
directory and for my fileserver, which is limited by a 100Mbps
connection to the rest of the network. I do not recommend it as a root
filesystem yet.

Cheers,
Eric


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-07-28  4:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-27  8:49 Porting Zfs features to ext2/3 postrishi
2008-07-27 22:49 ` Theodore Tso
2008-07-27 22:49   ` Shehjar Tikoo
2008-07-27 23:37     ` Theodore Tso
2008-07-28  3:42       ` Shehjar Tikoo
2008-07-27 22:54 ` Eric Anopolsky
2008-07-27 23:38   ` Theodore Tso
2008-07-28  4:15     ` Eric Anopolsky [this message]
2008-07-28 12:40       ` Theodore Tso
2008-07-29  3:58         ` Eric Anopolsky
2008-07-29 16:46           ` Ric Wheeler
2008-07-30  6:00             ` Eric Anopolsky
2008-07-29 21:00         ` Szabolcs Szakacsits
2008-07-29 22:52     ` Szabolcs Szakacsits
2008-07-30  1:29       ` Theodore Tso
2008-08-07 12:09         ` Goswin von Brederlow
2008-07-30  1:34       ` Theodore Tso
2008-07-31  0:50         ` Szabolcs Szakacsits
2008-08-04 20:38           ` Szabolcs Szakacsits
2008-08-07 12:01     ` Goswin von Brederlow

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=1217218559.28825.12.camel@telesto \
    --to=erpo41@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=postrishi@gmail.com \
    --cc=tytso@mit.edu \
    /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