David Sterba wrote on 2015/11/25 13:42 +0100:
On Tue, Nov 24, 2015 at 04:50:00PM +0800, Qu Wenruo wrote:
It seems the conflict is quite huge, your reiserfs support is based on
the old behavior, just like what old ext2 one do: custom extent allocation.
I'm afraid the rebase will take a lot of time since I'm completely a
newbie about reiserfs... :(
Yeah, the ext2 callbacks are abstracted and replaced by reiserfs
implementations, and the abstratction is quite direct. This might be a
problem with merging your patchset.
The abstraction is better than I expected, and should be quite handle to
use.
Although a lot of my codes will be changed to use it.
I may need to change a lot of ext2 direct call to generic one, and may
even change the generic function calls.(no alloc/free, only free space
lookup)
And some (maybe a lot) of reiserfs codes may be removed during the rework.
As far as the conversion support stays, it's not a problem of course. I
don't have a complete picture of all the actual merging conflicts, but
the idea is to provide the callback abstraction v2 to allow ext2 and
reiser plus allow all the changes of this pathcset.
Glad to hear that.
BTW, which reiserfs progs headers are you using?
It seems that the headers you are using is quite different from what my
distribution is providing, and this makes compile impossible.
For example, in my /usr/include/reiserfs, there is no io.h, no reiserfs.h.
No structure named reseifs_key, but only key.
Not sure if it is my progsreiserfs is too old or whatever other reason.
What progsreiserfs are you using?
Thanks,
Qu
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
