From: Christian Parpart <trapni@gentoo.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: autotoolized and splitup into {libbtrfs,tools,tests}
Date: Thu, 9 Oct 2008 08:47:43 +0200 [thread overview]
Message-ID: <200810090847.43559.trapni@gentoo.org> (raw)
In-Reply-To: <20081009055558.GB24531@infradead.org>
On Thursday 09 October 2008 07:55:58 Christoph Hellwig wrote:
> On Thu, Oct 09, 2008 at 04:20:49AM +0200, Christian Parpart wrote:
> > Hi,
> >
> > this now makes use of autoconf/automake/libtool suite,
> > thus, enabling a wider range of platforms etc.
> > Although, I've split up the build into tools, lib, and tests,
> > making it possible for 3rd-parties to link against libbtrfs now.
>
> I don't think allowing 3rd parties to link against it is a good idea.
> It's basically the kernel code with a few wrappers around it, and will
> change a lot over time.
I already noticed that, and this is another thing:
Why is the kernel module and the userland duplicating so much code?
As of ZFS, they've written a set of libraries (libzfs, libzpool, kernel compat
libs, ...) that are shared between userland and kernel, thus, making porting
to other platforms lots of easier.
If btrfs would do the same aproach, it could also benifit from a fuse frontend
(aside the kernel module) to be used for debugging purposes, think of gdb,
valgrind (or cachegrind) to mention the most interesting ones.
I talked to yangzheng about this, and he said that this just seems to lag a
volunteer to do, however, *after* the disk format is completed.
Regards,
Christian Parpart.
next prev parent reply other threads:[~2008-10-09 6:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 2:20 [PATCH] btrfs-progs: autotoolized and splitup into {libbtrfs,tools,tests} Christian Parpart
2008-10-09 5:55 ` Christoph Hellwig
2008-10-09 6:47 ` Christian Parpart [this message]
2008-10-09 10:45 ` David Woodhouse
2008-10-09 13:55 ` Christian Parpart
2008-10-09 21:52 ` Eric Anopolsky
2008-10-09 22:07 ` David Woodhouse
2008-10-10 1:01 ` Christian Parpart
2008-10-10 6:38 ` David Woodhouse
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=200810090847.43559.trapni@gentoo.org \
--to=trapni@gentoo.org \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.