linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: 인정식 <js7.in@samsung.com>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Re: Porting BTRFS to user space
Date: Tue, 07 Apr 2015 23:57:11 +0000 (GMT)	[thread overview]
Message-ID: <455311443.534051428451031043.JavaMail.weblogic@epmlwas09b> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=euc-kr, Size: 1807 bytes --]

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


------- Original Message -------
Sender : Austin S Hemmelgarn<ahferroin7@gmail.com> 
Date   : 2015-04-08 02:50 (GMT+09:00)
Title  : Re: Porting BTRFS to user space

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.
> It 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.

<p>&nbsp;</p><p>&nbsp;</p>ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±ý»k~ÏâžØ^n‡r¡ö¦zË\x1aëh™¨è­Ú&£ûàz¿äz¹Þ—ú+€Ê+zf£¢·hšˆ§~†­†Ûiÿÿïêÿ‘êçz_è®\x0fæj:+v‰¨þ)ߣøm

             reply	other threads:[~2015-04-07 23:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 23:57 인정식 [this message]
2015-04-08 11:37 ` Porting BTRFS to user space Austin S Hemmelgarn
  -- strict thread matches above, loose matches on Subject: below --
2015-04-08 12:03 인정식
2015-04-08 12:27 ` Hugo Mills

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=455311443.534051428451031043.JavaMail.weblogic@epmlwas09b \
    --to=js7.in@samsung.com \
    --cc=ahferroin7@gmail.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).