public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sébastien Wacquiez" <sw@enix.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs and raw zvol-like partition
Date: Sun, 12 Apr 2009 20:32:29 +0200	[thread overview]
Message-ID: <49E233BD.8050700@enix.org> (raw)
In-Reply-To: <2a31deca0904120613s56d8570pc1403284afcac094@mail.gmail.com>

Andrey Kuzmin a =C3=A9crit :
> zvol (interface) does not just  'export raw device' but rather
> implements volume  abstraction and integrates volume management into
> file-system.
>  =20
Yep. I suck at writing english, thanks for pointing that out :)

I surely mislead myself, but I think that the "volume management" of ZF=
S=20
could be done with file.

Alloc on write ? Use sparse file. Resizing ? Append or truncate the=20
file. Snapshot ? Snapshot the file. Another Volume ? An other file :)

In fact, the two thinks that have to be done, for me, is :
 1/ Optimise the different layer to bypass permission, acl, & co, and=20
surely the way data is written.
 2/ Be able to export those file directly as block device. (Allowing=20
some more optimisation :) )

It's why I called this feature "export raw device" (as in "export raw=20
file as block device"). As I say, it could be emulated with file and=20
loopback, but it'll surely be slow ... So I wanna know if btrfs plan to=
=20
have those type of optimization (and the user land tools to simplify=20
it's management).


Regards,


S=C3=A9bastien Wacquiez
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-04-12 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-12  7:26 Btrfs and raw zvol-like partition Sébastien Wacquiez
2009-04-12 13:13 ` Andrey Kuzmin
2009-04-12 18:32   ` Sébastien Wacquiez [this message]
2009-04-12 19:54     ` Andrey Kuzmin
2009-04-13 13:56 ` Chris Mason

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=49E233BD.8050700@enix.org \
    --to=sw@enix.org \
    --cc=linux-btrfs@vger.kernel.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