linux-bcachefs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@linux.dev>
To: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
	linux-bcachefs@vger.kernel.org
Subject: [LSF/MM/BPF TOPIC] bcachefs
Date: Wed, 22 Feb 2023 14:46:31 -0500	[thread overview]
Message-ID: <Y/ZxFwCasnmPLUP6@moria.home.lan> (raw)

Hi, I'd like to give an update on bcachefs progress and talk about
upstreaming.

There's been a lot of activity over the past year or so:
 - allocator rewrite
 - cycle detector for deadlock avoidance
 - backpointers
 - test infrastructure!
 - starting to integrate rust code (!)
 - lots more bug squashing, scalability work, debug tooling improvements

I'd like to talk more about where things are at, long term goals, and
finally upstreaming this beast.

             reply	other threads:[~2023-02-22 19:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 19:46 Kent Overstreet [this message]
2023-03-07  5:01 ` [LSF/MM/BPF TOPIC] bcachefs Darrick J. Wong
2023-03-07  6:12   ` Kent Overstreet
2023-03-07  7:25 ` Matthew Wilcox
2023-03-07  7:59   ` Kent Overstreet
  -- strict thread matches above, loose matches on Subject: below --
2024-01-01 22:56 Kent Overstreet
2024-01-02  8:02 ` Viacheslav Dubeyko
2024-01-02 16:05   ` Kent Overstreet
2024-01-03  7:39     ` Viacheslav Dubeyko
2024-01-03 17:52       ` Kent Overstreet
2024-01-03 19:22         ` Carl E. Thompson
2024-01-03 22:26           ` Kent Overstreet
2024-01-04  7:43         ` Viacheslav Dubeyko
2021-06-02 23:07 Kent Overstreet
2021-06-30 18:18 ` Dan Robertson

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=Y/ZxFwCasnmPLUP6@moria.home.lan \
    --to=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-fsdevel@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).