Improved allocator threading
I wanted to work on the allocator with a larger scope
where threading is only a minor part of trying to address
these items from the Project_ideas that I think could change
disk format in some way (to fix it before v1.0):
- Different sector sizes
- Multiple chunk trees and extent allocation trees
- Limiting btree failure domains
and maybe impacting this from Development_timeline
- Reserved space for online fsck and the ability to add
storage so that a background extent allocation check can proceed
Maybe this is too ambitious or I am seeing intersections that
are not there, but I am prepared to try doing the allocator.
jim
P.S. Are there other V1.0 format issues to lock down that
should be worked before the missing features like O_DIRECT?
--
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