linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@gmail.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	lsf-pc@lists.linux-foundation.org
Subject: [LSF/MM/BPF TOPIC] bcachefs
Date: Wed, 16 Feb 2022 02:44:33 -0500	[thread overview]
Message-ID: <20220216074433.u726dkh2q2wdtwne@zaphod.evilpiepirate.org> (raw)

Hi, I'd like to come give an update on bcachefs.

It's been a long road going from bcache, and starting with what was essentially
a prototype for a new filesystem, and turning it into a real (scalable, robust,
full featured) filesystem.

Over the past few years, we've added reflink, subvolumes and snapshots. I'm
particularly proud of how snapshots turned out - it's roughly a versioned btree
approach, and it's scalable and fast, even fsck is O(number of keys of
metadata), not O(number of snapshots). I've got it up to a million snapshots in
a test VM.

The bigger thing though is that the core fundamentals are pretty close to done -
replacing all the "periodically walk the world" algorigthms with real persistent
data structures that scale. A big allocator rewrite is about to land, and after
that will be backpointers - to fix copygc scanning.

Things are in flux lately with all the allocator work, but I'm hoping once that
settles down and I've worked through the backlog of bug reports and performance
regressions, we might be ready for upstreaming sometime this year...

                 reply	other threads:[~2022-02-16  7:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220216074433.u726dkh2q2wdtwne@zaphod.evilpiepirate.org \
    --to=kent.overstreet@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).