All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH v2 0/4] Folio pos + size cleanups
Date: Tue, 10 Jun 2025 14:17:44 +0200	[thread overview]
Message-ID: <cover.1749557686.git.dsterba@suse.com> (raw)

Helper to simplify numerous folio_pos() + folio_size() calculations.

v2:
- preparatory patches: rename variables matching the semantics of
  locking with the "-1" end of range, and simplify some range calculations
- updated changelogs with stats of potential usage outside of btrfs

David Sterba (4):
  btrfs: simplify range end calculations in
    truncate_block_zero_beyond_eof()
  btrfs: rename variables for locked range in defrag_prepare_one_folio()
  btrfs: add helper folio_end()
  btrfs: use folio_end() where appropriate

 fs/btrfs/compression.h  |  7 +++----
 fs/btrfs/defrag.c       | 19 +++++++++----------
 fs/btrfs/extent_io.c    | 17 ++++++++---------
 fs/btrfs/file.c         |  9 ++++-----
 fs/btrfs/inode.c        | 12 +++++-------
 fs/btrfs/misc.h         |  7 +++++++
 fs/btrfs/ordered-data.c |  2 +-
 fs/btrfs/subpage.c      |  5 ++---
 8 files changed, 39 insertions(+), 39 deletions(-)

-- 
2.47.1


             reply	other threads:[~2025-06-10 12:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 12:17 David Sterba [this message]
2025-06-10 12:17 ` [PATCH v2 1/4] btrfs: simplify range end calculations in truncate_block_zero_beyond_eof() David Sterba
2025-06-11 10:26   ` Johannes Thumshirn
2025-06-10 12:17 ` [PATCH v2 2/4] btrfs: rename variables for locked range in defrag_prepare_one_folio() David Sterba
2025-06-10 12:17 ` [PATCH v2 3/4] btrfs: add helper folio_end() David Sterba
2025-07-29  9:59   ` Andreas Gruenbacher
2025-07-30 21:58     ` Matthew Wilcox
2025-08-04 13:14       ` David Sterba
2025-06-10 12:17 ` [PATCH v2 4/4] btrfs: use folio_end() where appropriate David Sterba
2025-06-11 10:27 ` [PATCH v2 0/4] Folio pos + size cleanups Johannes Thumshirn

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.1749557686.git.dsterba@suse.com \
    --to=dsterba@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.