diff options
author | Killian De Volder <killian.de.volderc@megasoft.be> | 2017-04-01 12:17:21 +0200 |
---|---|---|
committer | Killian De Volder <killian.de.volderc@megasoft.be> | 2017-04-01 12:17:21 +0200 |
commit | 7c21019184846d04d92b35bb6b0739bc009dcadf (patch) | |
tree | 466d1d69d3dc10be359a65c1289da8933e5fa03a | |
parent | 306cbe00b913bb7ce5ab85bf7b970251751fe254 (diff) | |
parent | a0a1f415b0d7b3f059cedb0fcde0b4db6f8528d1 (diff) |
Merge branch 'master' of ssh://evilpiepirate.org:22/home/bcachefs/bcachefs
-rw-r--r-- | Todo.mdwn | 14 | ||||
-rw-r--r-- | index.mdwn | 6 |
2 files changed, 17 insertions, 3 deletions
@@ -15,6 +15,18 @@ is implementing a new kind of reservation of journal space for the new, long running transactions. + * Allocation information (currently just bucket generation numbers & priority + numbers, for LRU caching) needs to be moved into a btree, and we need to + start persisting actual allocation information so we don't have to walk all + extents at mount time. + + Just moving the existing prios/gens to a btree will be a significant + improvement - besides getting us incrementally closer to persisting full + allocation information, the existing code is a rather hacky mechanism dating + from the early days of bcache and has recently been the source of an annoying + bug due to the design being a bit fragile, and it'll be a performance + improvement since it'll get rid of the last source of forced journal flushes. + ### Other * When we're using compression, we end up wasting a fair amount of space on @@ -56,6 +68,8 @@ ## Developers + * End user documentation needs a lot of work - complete man pages, etc. + * bcachefs-tools needs some fleshing out in the --help department * Write a tool to benchmark tail-latency. @@ -24,6 +24,9 @@ incremental development, and keeping things stable, and aggressively fixing design issues as they are found; the bcachefs codebase is considerably more robust and mature than upstream bcache. +Fixing bugs always take priority over features! This means getting features out +takes longer, but for a filesystem not losing your data is the biggest feature. + Developing a filesystem is also not cheap or quick or easy; we need funding! Please chip in on [[Patreon|https://www.patreon.com/bcachefs]] - the Patreon page also has more information on the motivation for bcachefs and the state of @@ -138,6 +141,3 @@ necessary, but I'm not expecting any more incompatible disk format changes. This will be addressed in the future - mount times will likely be the next big push after the next big batch of on disk format changes. - -## [[Todo]] list - |