From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: Anand Jain <anand.jain@oracle.com>,
linux-btrfs@vger.kernel.org, Jeff Mahoney <jeffm@suse.com>,
David Sterba <dsterba@suse.com>
Subject: Re: [RFC] Converging userspace and kernel code
Date: Tue, 10 Jan 2017 10:04:56 -0600 [thread overview]
Message-ID: <d0c2e05d-0b7a-a782-80b8-e1776e7b6fdb@suse.de> (raw)
In-Reply-To: <d0a11a09-322d-89bc-1a15-598f6a14e6be@oracle.com>
On 01/10/2017 09:20 AM, Anand Jain wrote:
>
>
> On 01/10/17 20:14, Goldwyn Rodrigues wrote:
>>
>>
>> On 01/09/2017 09:28 PM, Anand Jain wrote:
>>>
>>> Goldwyn,
>>>
>>> Could you add a list what functionality in btrfs-progs will
>>> be using the 'core'. ?
>>
>>
>> There are too many to list. It would contain the algorithmic functions
>> of btrfs which would be able to interact with both kernel and
>> btrfs-progs.
>
> I am getting confused. How about a few from the btrfs-progs ?
>
>
Functions such as open_ctree(), or the set/get functions. The idea is to
keep the codebase of this core component the same in btrfs-progs and kernel.
As an example, see how XFS have done using libxfs. Something around the
same lines.
--
Goldwyn
next prev parent reply other threads:[~2017-01-10 16:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 13:16 [RFC] Converging userspace and kernel code Goldwyn Rodrigues
2017-01-09 2:11 ` Qu Wenruo
2017-01-09 9:31 ` Christoph Hellwig
2017-01-09 12:06 ` Goldwyn Rodrigues
2017-01-10 0:35 ` Qu Wenruo
2017-01-10 0:56 ` Omar Sandoval
2017-01-09 15:31 ` Eric Sandeen
2017-01-09 21:34 ` Omar Sandoval
2017-01-09 21:38 ` Jeff Mahoney
2017-01-10 1:46 ` Darrick J. Wong
2017-01-10 2:24 ` Qu Wenruo
2017-01-10 3:28 ` Anand Jain
2017-01-10 12:14 ` Goldwyn Rodrigues
2017-01-10 15:20 ` Anand Jain
2017-01-10 16:04 ` Goldwyn Rodrigues [this message]
2017-01-11 2:23 ` Anand Jain
2017-01-11 2:32 ` Qu Wenruo
2017-01-11 2:55 ` Goldwyn Rodrigues
2017-01-11 10:58 ` Anand Jain
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=d0c2e05d-0b7a-a782-80b8-e1776e7b6fdb@suse.de \
--to=rgoldwyn@suse.de \
--cc=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--cc=jeffm@suse.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).