Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
	David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: simplify dirty buffer tracking
Date: Mon, 15 May 2023 21:22:50 +0200	[thread overview]
Message-ID: <20230515192256.29006-1-hch@lst.de> (raw)

Hi all,

this series rewrites the tracking and writeback of the per-transaction
or per-tree_log dirty buffers.  It is intended as a first step towards
getting rid of btree_inode, but turns out to be a pretty nice cleanup
on it's own.  I also see minor speedup in fs_mark workloads, but given
how variable they are in general I'm not sure if they really matter.

This series starts out new extent_buffer.[ch].  I plan to eventually
concentrate all code for extent_buffer handling there, but for now
this just has brand-new code.

Note that the series is based on top of net-next because the previous
round of extent_buffer changes has not made it to misc-next yet.

Diffstat:
 fs/btrfs/Makefile                |    2 
 fs/btrfs/ctree.h                 |    3 
 fs/btrfs/disk-io.c               |   72 +++++--------
 fs/btrfs/extent-io-tree.c        |  212 ---------------------------------------
 fs/btrfs/extent-io-tree.h        |   14 --
 fs/btrfs/extent-tree.c           |   21 ---
 fs/btrfs/extent_buffer.c         |  104 +++++++++++++++++++
 fs/btrfs/extent_buffer.h         |   26 ++++
 fs/btrfs/extent_io.c             |  131 ++++++------------------
 fs/btrfs/extent_io.h             |    2 
 fs/btrfs/fs.h                    |    3 
 fs/btrfs/tests/extent-io-tests.c |    2 
 fs/btrfs/transaction.c           |  168 ++----------------------------
 fs/btrfs/transaction.h           |    3 
 fs/btrfs/tree-log.c              |   71 ++++++++-----
 fs/btrfs/zoned.c                 |   11 +-
 include/trace/events/btrfs.h     |   57 ----------
 17 files changed, 278 insertions(+), 624 deletions(-)

             reply	other threads:[~2023-05-15 19:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 19:22 Christoph Hellwig [this message]
2023-05-15 19:22 ` [PATCH 1/6] btrfs: use a linked list for tracking per-transaction/log dirty buffers Christoph Hellwig
2023-05-17 10:40   ` Filipe Manana
2023-05-17 12:21     ` Christoph Hellwig
2023-05-17 16:24       ` Filipe Manana
2023-05-17 16:37         ` Christoph Hellwig
2023-05-15 19:22 ` [PATCH 2/6] btrfs: remove convert_extent_bit Christoph Hellwig
2023-05-15 19:22 ` [PATCH 3/6] btrfs: directly wait for buffer writeback completion in btrfs_wait_buffers Christoph Hellwig
2023-05-15 19:22 ` [PATCH 4/6] btrfs: move dropping the bg reference out of submit_eb_page Christoph Hellwig
2023-05-15 19:22 ` [PATCH 5/6] btrfs: move locking and write pointer checking into write_one_eb Christoph Hellwig
2023-05-15 19:22 ` [PATCH 6/6] btrfs: bypass filemap_fdatawrite_range in btrfs_write_buffers Christoph Hellwig

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=20230515192256.29006-1-hch@lst.de \
    --to=hch@lst.de \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@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