public inbox for linux-bcachefs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: linux-bcachefs@vger.kernel.org
Subject: [PATCH 0/2] bcachefs: fiemap delalloc support and cleanup
Date: Tue, 19 Dec 2023 09:02:13 -0500	[thread overview]
Message-ID: <20231219140215.300753-1-bfoster@redhat.com> (raw)

Hi,

Here's a couple patches to add basic fiemap support for delalloc extents
and make a somewhat unrelated cleanup. Patch 1 formats delalloc data
into fiemap info by faking up an extent key for pagecache resident
extents. When reading through some related code to grok how to do that
(I initially used a reservation type key), I happened across
bch2_extent_fallocate(), found the associated logic a bit wonky, and
thus tried to clean it up. Both patches are available in my CI test
branch.

Thoughts, reviews, flames appreciated.

Brian

P.S., I'm off soonish for PTO. If there are any issues to be addressed
with these patches, I'll pick it back up after the New Year.

Brian Foster (2):
  bcachefs: add fiemap delalloc extent detection
  bcachefs: clean up some dead fallocate code

 fs/bcachefs/fs.c      | 60 ++++++++++++++++++++++++++++++++++++++++---
 fs/bcachefs/io_misc.c | 35 +++++++++----------------
 2 files changed, 68 insertions(+), 27 deletions(-)

-- 
2.42.0


             reply	other threads:[~2023-12-19 14:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 14:02 Brian Foster [this message]
2023-12-19 14:02 ` [PATCH 1/2] bcachefs: add fiemap delalloc extent detection Brian Foster
2023-12-19 23:57   ` Kent Overstreet
2024-01-04 12:12     ` Brian Foster
2024-01-04 23:41       ` Kent Overstreet
2024-01-08 15:33         ` Brian Foster
2024-01-08 22:34           ` Carl E. Thompson
2024-01-09 16:42             ` Brian Foster
2024-01-10 21:54               ` Carl E. Thompson
2023-12-19 14:02 ` [PATCH 2/2] bcachefs: clean up some dead fallocate code Brian Foster
2023-12-20  0:00   ` Kent Overstreet

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=20231219140215.300753-1-bfoster@redhat.com \
    --to=bfoster@redhat.com \
    --cc=linux-bcachefs@vger.kernel.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