xfs
[Top] [All Lists]

Re: [PATCH 00/28] xfsprogs: sparse inode chunks

To: Brian Foster <bfoster@xxxxxxxxxx>
Subject: Re: [PATCH 00/28] xfsprogs: sparse inode chunks
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Tue, 16 Jun 2015 10:33:44 +1000
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <1433270521-62026-1-git-send-email-bfoster@xxxxxxxxxx>
References: <1433270521-62026-1-git-send-email-bfoster@xxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Tue, Jun 02, 2015 at 02:41:33PM -0400, Brian Foster wrote:
> Hi all,
> 
> Now that the sparse inode chunks feature is merged into the kernel tree
> for 4.2, here is the first official drop of userspace support. This
> series is based on the current libxfs-4.1-update branch.
> 
> Patches 1-10 are libxfs infrastructure and correspond to the similarly
> named kernel patches. The bits not relevant to userspace are dropped
> along with the bulk of the sparse inode chunk allocation logic from the
> kernel due to the combination of non-existent dependencies in userspace
> (e.g., xfs_bit.c) and the fact that this code isn't invoked from
> userspace.

Ok, so this is causing problems with merging other code into
userspace. What I'm trying to do is keepthe kernel fs/xfs/libxfs/
code as close to identical with the xfsprogs libxfs/ code so that
patches just port straight across. I came across this difference
because my rmap btree patches fail to apply cleanly to xfs_ialloc.c
and it's because of all this missing code in userspace.

Rather than wait another day or two for you to rework this, Brian,
I'm simply going to rework this series to pull all the kernel patches
across and make it compile in userspace so that I can pull all the
rmap btree stuff across without needing to rework bits and peices of
the patchset.

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>