On 05/27/2016 06:55 PM, David Sterba wrote:
On Fri, May 27, 2016 at 09:38:09AM +0800, Qu Wenruo wrote:
Since btrfs-convert has been reworked to use a completely new method to
do such allocation, now it doesn't need any custom_alloc_extent() function.
And its new chunk lay out is designed to only put metadata chunk into
large enough unused space, and data chunks will cover all used space.
So there is no need for such patch AFAIK.
I agree, and I think that the motivation for the convert rewrite was the
same problem that these patches address.
And the new convert is already in devel branch.
The plan is to release 4.6 with this patchset, I'm still not decided
about the low-mem mode for checker.
For low memory mode, at least we're not that eager to see it merged into
4.6.
Although if it could be merged, it would make us free from rebasing it
again and again.
But the problem is, for end-user, we are cheating them, as the low
memory mode is not really that low memory.
Since fs tree is still eating tons of memory.
Thanks,
Qu
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
