Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/5] btrfs: some optimizations and cleanups for log syncing
Date: Wed, 22 Jul 2026 16:24:37 +0100	[thread overview]
Message-ID: <cover.1784733395.git.fdmanana@suse.com> (raw)
In-Reply-To: <cover.1784656641.git.fdmanana@suse.com>

From: Filipe Manana <fdmanana@suse.com>

Some optimizations for log syncing, specially for non-sdd mounts, and
some cleanups. Details in the changelogs of each patch.

V2: Removed two patches which sashiko found problematic, the benefits of
    fixing them up versus the complexity required to fix them is not worth
    it. Updated last patch to add the data_race() annotation in the trace
    events.

Filipe Manana (5):
  btrfs: stop sleeping for one jiffy in non-ssd mounts during log commit
  btrfs: remove log batch counter use for fsync
  btrfs: move condition for log commit wait into wait_log_commit()
  btrfs: check for exit condition after waking in wait_log_commit()
  btrfs: use simple booleans for log_commit field in struct btrfs_root

 fs/btrfs/ctree.h             |  6 +--
 fs/btrfs/disk-io.c           |  3 --
 fs/btrfs/file.c              |  4 --
 fs/btrfs/transaction.c       |  8 +---
 fs/btrfs/tree-log.c          | 85 ++++++++++++------------------------
 include/trace/events/btrfs.h |  4 +-
 6 files changed, 32 insertions(+), 78 deletions(-)

-- 
2.47.2


  parent reply	other threads:[~2026-07-22 15:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 12:41 [PATCH 0/7] btrfs: some optimizations and cleanups for log syncing fdmanana
2026-07-22 12:41 ` [PATCH 1/7] btrfs: stop sleeping for one jiffy in non-ssd mounts during log commit fdmanana
2026-07-22 12:41 ` [PATCH 2/7] btrfs: remove log batch counter use for fsync fdmanana
2026-07-22 12:41 ` [PATCH 3/7] btrfs: do an initial lockless committed log transaction check during log syncing fdmanana
2026-07-22 12:41 ` [PATCH 4/7] btrfs: check for log writers count first in wait_for_writer() fdmanana
2026-07-22 12:41 ` [PATCH 5/7] btrfs: move condition for log commit wait into wait_log_commit() fdmanana
2026-07-22 12:41 ` [PATCH 6/7] btrfs: check for exit condition after waking in wait_log_commit() fdmanana
2026-07-22 12:41 ` [PATCH 7/7] btrfs: use simple booleans for log_commit field in struct btrfs_root fdmanana
2026-07-22 15:19 ` [PATCH 0/7] btrfs: some optimizations and cleanups for log syncing Boris Burkov
2026-07-22 15:24 ` fdmanana [this message]
2026-07-22 15:24   ` [PATCH v2 1/5] btrfs: stop sleeping for one jiffy in non-ssd mounts during log commit fdmanana
2026-07-22 15:24   ` [PATCH v2 2/5] btrfs: remove log batch counter use for fsync fdmanana
2026-07-22 15:24   ` [PATCH v2 3/5] btrfs: move condition for log commit wait into wait_log_commit() fdmanana
2026-07-22 15:24   ` [PATCH v2 4/5] btrfs: check for exit condition after waking in wait_log_commit() fdmanana
2026-07-22 15:24   ` [PATCH v2 5/5] btrfs: use simple booleans for log_commit field in struct btrfs_root fdmanana
2026-07-22 15:35   ` [PATCH v2 0/5] btrfs: some optimizations and cleanups for log syncing Jeff Layton

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=cover.1784733395.git.fdmanana@suse.com \
    --to=fdmanana@kernel.org \
    --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