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 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*jg?????/??z??2???&?)ߡ?????h??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.

 

 

{.n++%ݶw{.n+{k~^nrzh&zzޗ++zfh~iz_j:+v)ߣm