From: Andy Grover <agrover@redhat.com>
To: Zach Brown <zab@redhat.com>
Cc: dsterba@suse.cz, Hugo Mills <hugo@carfax.org.uk>,
penn43@gmx.com, linux-btrfs@vger.kernel.org
Subject: Re: Writing a wtapper for BTRFS
Date: Wed, 27 Feb 2013 14:48:36 -0800 [thread overview]
Message-ID: <512E8D44.1050001@redhat.com> (raw)
In-Reply-To: <20130227213421.GO1658@lenny.home.zabbo.net>
On 02/27/2013 01:34 PM, Zach Brown wrote:
> On Wed, Feb 27, 2013 at 04:19:57PM +0100, David Sterba wrote:
>> On Wed, Feb 27, 2013 at 01:08:46PM +0000, Hugo Mills wrote:
>>> You may want to look at the btrfs-progs libify patches (posted to
>>> this list in the last couple of months), which try to pull out the
>>> more useful bits of btrfs-progs as a userspace C API.
>>
>> FYI, libify patch will be in the next integration branch.
>>
>>> You may also want to look at the bits I implemented in python[2]
>>> for a subset of the btrfs ioctls and data structures in btrfs-gui.
>>>
>>> Other than that, it's down to the data structures documentation on
>>> the wiki[1], and reading through ioctl.h.
>>
>> bedup https://github.com/g2p/bedup does python binding, in a different
>> way than btrfs-gui.
>
> Andy also mentioned being interested in language bindings of a libified
> btrfs-progs, cc:ing.
Yeah. Python/otherlang wrappers around a btrfs-progs C api seem
preferable to each binding calling ioctls themselves, no? I think every
common language is going to eventually want a btrfs lib.
-- Andy
next prev parent reply other threads:[~2013-02-27 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 12:53 Writing a wtapper for BTRFS penn43
2013-02-27 13:08 ` Hugo Mills
2013-02-27 15:19 ` David Sterba
2013-02-27 21:34 ` Zach Brown
2013-02-27 22:48 ` Andy Grover [this message]
2013-02-28 13:43 ` Writing a wrapper " penn43
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=512E8D44.1050001@redhat.com \
--to=agrover@redhat.com \
--cc=dsterba@suse.cz \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=penn43@gmx.com \
--cc=zab@redhat.com \
/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).