On 2017年09月28日 00:20, David Sterba wrote:
On Mon, Sep 25, 2017 at 07:15:30AM -0400, Austin S. Hemmelgarn wrote:
On 2017-09-24 10:08, Goffredo Baroncelli wrote:
On 09/24/2017 12:10 PM, Anand Jain wrote:
A lot of points in this thread, let me address them here.
I don't want to remove --rootdir functionality, the fix that's being
proposed removes the minimalization -- feature that was not well known,
but I understand it's useful (and already used).
I'd like to fix that in another way, eg. as an option to mkfs or a
separate tool.
I'm not worried about adding more code or code complexity. If we do it
right it's not a problem in the long run. But people for some reason
like to delete other people's code or functionality.
Regarding guessing number of users, this is always hard. So if there's
one vocal enough to let us know about the usecase, it's IMHO good time
to explore the it, code-wise and documentation-wise, and fix it or
improve.
So, what next. I'd like to get rid of the custom chunk allocator, namely
because of the known 1MB area misuse and duplication.
Implementing the minimalization might need some preparatory work and I
don't have a realistic ETA now.
Well, if using over-reserve-then-shrink method, it could be done,
without much hassle.
However ETA maybe delayed to middle of Oct, as I'm going to enjoy my
holiday during 1st Oct to 7th Oct.
Thanks,
Qu
Ideally we'd fix both problems in one
version, as I'd rather avoid "temporary" solution to drop the
minimalization with the promise to put it back later.
--
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
