From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: js7.in@samsung.com,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Porting BTRFS to user space
Date: Wed, 08 Apr 2015 07:37:13 -0400 [thread overview]
Message-ID: <552512E9.2090805@gmail.com> (raw)
In-Reply-To: <455311443.534051428451031043.JavaMail.weblogic@epmlwas09b>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
On 2015-04-07 19:57, 인정식 wrote:
> Thank you for the information.
> I just found that btrfs-progs includes several files that seem modified from btrfs kernel source.
> I am not sure exactly what they are.
> Web pages say libbtrfs is to provide interface for apps that use btrfs.
> Why should there be duplicated codes between kernel and user space?
> Is it an on-going effort to port whole btrfs to user space?
>
> Could you lead me to some more information about libbtrfs or how to port btrfs to user space?
>
> Thank you,
> Jeongsik
>
>
As far as I understand it, the intent is to allow things like btrfs
check and btrfs restore to still work even if the kernel doesn't have
btrfs support. From what I can tell, you are the first person to
actually be serious about getting BTRFS running in userspace, so there
probably isn't much BTRFS specific literature out there.
I would, however suggest looking at the FUSE drivers for ext4 and ZFS,
as those are both ported from kernel space, and should give some good
examples of where to start.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2967 bytes --]
next prev parent reply other threads:[~2015-04-08 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 23:57 Re: Porting BTRFS to user space 인정식
2015-04-08 11:37 ` Austin S Hemmelgarn [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-04-08 12:03 인정식
2015-04-08 12:27 ` Hugo Mills
2015-04-08 13:13 ` Chris Samuel
2015-04-08 13:38 ` Stef Bon
2015-04-07 1:28 인정식
2015-04-07 17:50 ` Austin S Hemmelgarn
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=552512E9.2090805@gmail.com \
--to=ahferroin7@gmail.com \
--cc=js7.in@samsung.com \
--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;
as well as URLs for NNTP newsgroup(s).