Hi Kent,
Zitat von Kent Overstreet <kent.overstreet@xxxxxxxxx>:
The code is definitely ready for wider usage, so I'm starting to work more on
the website and documentation - have a look:
https://bcache.evilpiepirate.org/Bcachefs/
Comments (and help with documentation!) appreciated.
thank you for starting that separate information block. It already
answers one of my main questions - "why should I use bcachefs instead
of bcache?" - and one statement there let me take a look at the Bcache
page:
"the bcachefs codebase is considerably more robust and mature than
upstream bcache"
(the following statements relate to the bcache page, so they don't fit
the "comments on bcachefs docs" request ;) )
As I still see "bcache" as the proper solution to fit *my* needs (see
below), I'm of course interested to run code that's as robust and
mature as can be. What I was looking for on the bcache page was
information on some bcache repository containing "more robust and
mature than upstream bcache" code and how to merge that into current
mainline kernels. For me, that was left unanswered.
Looking at the bcache page I see:
"Bcache has been merged into the mainline Linux kernel; for the latest
stable bcache release use the latest 3.10 or 3.11 stable kernel."
Wasn't much effort put into pulling the latest bcache patches into the
4.x mainline kernel? And it might be interesting to mention if/which
distro maintainers (i. e. SUSE, the only one I know of for sure) put
patches and updates into their distributed kernels, likely making
their kernels more robust and mature than upstream (WRT bcache).
I understand that your current focus is on bcachefs, but as I need to
provide fast block storage back-ends to i. e. DRBD, I'm stuck with
bcache (as a substitute for storage controllers with integrated
SSD/flash cache). Hence my comments here - and they are meant as
*comments*, not complaints.
Regards,
Jens
--
To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
