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: Tue, 07 Apr 2015 13:50:32 -0400 [thread overview]
Message-ID: <552418E8.6060509@gmail.com> (raw)
In-Reply-To: <759287502.475491428370096552.JavaMail.weblogic@epmlwas09d>
[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]
On 2015-04-06 21:28, 인정식 wrote:
> Hello BTRFS developers,
>
> I am requesting your opion.
>
> I am planning to design and implement DFS version of BTRFS.
> Roughly it will be done by
> 1. Extending current DeviceID to NodeID:DeviceID to support multi-node, and
> 2. Implementing inter-node data and meta-data access over TCP.
> Do you think it would be feasible?
>
> For development, I would like to port the kernel code to user space.
> I could continue to run in user mode or be ported back to kernel space.
> But I don't know how can I start to porting the kernel code to user space.
> Is there anyone who can help?
>
> Thanks,
> JeongsikN떑꿩�r툤y鉉싕b쾊Ф푤v�^�)頻{.n�+돴쪐{켷雹�)�鍊w*\x1fjgП�\x1e텎쉸듶줷/곴�z받뻿�2듷솳鈺�&�)傘첺뛴\x7f�\x1e췍쳺�h�\x0f�j:+v돣둾�明
>
Personally, my suggestion would be to start with a port to FUSE, and
then start implementing your modifications off of that. That said, much
of the code should already be available in userspace through libbtrfs,
which is packaged with btrfs-progs.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2967 bytes --]
next prev parent reply other threads:[~2015-04-07 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 1:28 Porting BTRFS to user space 인정식
2015-04-07 17:50 ` Austin S Hemmelgarn [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-04-07 23:57 인정식
2015-04-08 11:37 ` Austin S Hemmelgarn
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
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=552418E8.6060509@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.