From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Anand Jain <anand.jain@oracle.com>, Moviuro <moviuro@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs-progs and btrfs(8) inconsistencies
Date: Fri, 5 Feb 2016 07:59:04 -0500 [thread overview]
Message-ID: <56B49C98.7060406@gmail.com> (raw)
In-Reply-To: <56B412FC.8060007@oracle.com>
On 2016-02-04 22:11, Anand Jain wrote:
>
>
> If you look critically we have been using UI/CLI as API,
> IMO these two class of interfaces be distinct clearly.
>
> Btrfs needs library functions/APIs which is callable in
> popular scripting language like python.
>
I wholeheartedly agree. At a minimum, we need to get our C API properly
in line. I'm not certain how closely libbtrfs matches the btrfs CLI,
but I'm pretty sure we have all the functionality needed for language
bindings there, we just need to solidify the API (or at least figure out
some way to properly version it). One thing I would love to see added
to both libbtrfs and the CLI though is some way to make EXTENT_SAME
ioctl calls on arbitrary extents, there's no way to do this without
writing your own program, and calling arbitrary ioctls from Python or
Java or any number of other languages is decidedly non-trivial compared
to C or C++.
next prev parent reply other threads:[~2016-02-05 13:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 21:54 btrfs-progs and btrfs(8) inconsistencies Moviuro
2016-02-04 1:33 ` Qu Wenruo
2016-02-04 8:57 ` Moviuro
2016-02-04 9:15 ` Qu Wenruo
2016-02-04 10:14 ` Martin Steigerwald
2016-02-04 12:04 ` Moviuro
2016-02-04 12:53 ` Austin S. Hemmelgarn
2016-02-04 19:40 ` Chris Murphy
2016-02-04 20:19 ` Austin S. Hemmelgarn
2016-02-04 20:40 ` Moviuro
2016-02-05 13:04 ` Austin S. Hemmelgarn
2016-02-04 17:17 ` Goffredo Baroncelli
2016-02-04 19:48 ` Hugo Mills
2016-02-04 20:10 ` Chris Murphy
2016-02-04 18:22 ` Chris Murphy
2016-02-05 3:11 ` Anand Jain
2016-02-05 12:59 ` Austin S. Hemmelgarn [this message]
2016-02-06 21:35 ` Chris Murphy
2016-02-07 10:07 ` Qu Wenruo
2016-02-07 20:26 ` Goffredo Baroncelli
2016-03-08 16:02 ` David Sterba
2016-03-09 10:02 ` Moviuro
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=56B49C98.7060406@gmail.com \
--to=ahferroin7@gmail.com \
--cc=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=moviuro@gmail.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).