linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
	linux-bcachefs@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] bcachefs
Date: Mon, 6 Mar 2023 21:01:46 -0800	[thread overview]
Message-ID: <20230307050146.GA1637838@frogsfrogsfrogs> (raw)
In-Reply-To: <Y/ZxFwCasnmPLUP6@moria.home.lan>

On Wed, Feb 22, 2023 at 02:46:31PM -0500, Kent Overstreet wrote:
> 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

XFS has rather a lot of locks and no ability to unwind a transaction
that has already dirtied incore state.  I bet you and I could have some
very interesting discussions about how to implement robust tx undo in a
filesystem.

(Not sure the /rest/ of the lsf crowd are going to care, but I do.)

>  - backpointers
>  - test infrastructure!

<cough> "test dashboard that we can all share" ?

>  - starting to integrate rust code (!)

I'm curious to hear about this topic, because I look at rust, and I look
at supercomplex filesystem code and wonder how in the world we're ever
going to port a (VERY SIMPLE) filesystem to Rust.  Now that I'm nearly
done with online repair for XFS, there's a lot of stupid crap about C
that I would like to start worrying about less because some other
language added enough guard rails to avoid the stupid.

>  - 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.

Go for it, I say.

--D

  reply	other threads:[~2023-03-07  5:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 19:46 [LSF/MM/BPF TOPIC] bcachefs Kent Overstreet
2023-03-07  5:01 ` Darrick J. Wong [this message]
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
2022-02-16  7:44 Kent Overstreet
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=20230307050146.GA1637838@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=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).