Skip to content

Avoid setting folio->private

Goldwyn Rodrigues linux-btrfs 2 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest2 patches 4 repliesIn review
  2. v12 patches 3 repliesSuperseded

Changes in v2 from the cover letter

- Incorporated Dave Sterba's comments

Patches in v2 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2btrfs: add mapping_set_release_always to inode's mappingfs/btrfs/extent_io.c fs/btrfs/file.c fs/btrfs/inode.c+5 -20 replies
2/2btrfs: kill EXTENT_FOLIO_PRIVATEfs/btrfs/compression.c fs/btrfs/defrag.c fs/btrfs/extent_io.c +6 more+22 -804 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.

Read the v2 thread

Cover letter [PATCH v2 0/2] Avoid setting folio->private

From: Goldwyn Rodrigues <[email protected]>

folio->private was set in order to get release_folio() callbacks. Instead if we set address_space flags AS_RELEASE_ALWAYS, there is no need to set EXTENT_FOLIO_PRIVATE on every folio->private.

These patches are posted so we don't face conflicts with iomap's iomap_folio_state, which also resides in folio->private.

Changes since v1:
- Incorporated Dave Sterba's comments

Goldwyn Rodrigues (2):
btrfs: add mapping_set_release_always to inode's mapping
btrfs: kill EXTENT_FOLIO_PRIVATE

 fs/btrfs/compression.c      |  2 +-
 fs/btrfs/defrag.c           |  2 +-
 fs/btrfs/extent_io.c        | 61 ++++++-------------------------------
 fs/btrfs/extent_io.h        | 10 ++----
 fs/btrfs/file.c             |  6 ++--
 fs/btrfs/free-space-cache.c |  9 ------
 fs/btrfs/inode.c            | 13 +++++---
 fs/btrfs/reflink.c          |  2 +-
 fs/btrfs/relocation.c       |  4 +--
 9 files changed, 27 insertions(+), 82 deletions(-)
Signature · 1 line
2.48.1