All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: chandanbabu@kernel.org, djwong@kernel.org
Cc: hch@lst.de, linux-xfs@vger.kernel.org
Subject: [GIT PULL 2/6] xfs: clean up realtime type usage
Date: Fri, 20 Oct 2023 15:17:30 -0700	[thread overview]
Message-ID: <169781767994.780878.672267596860381813.stg-ugh@frogsfrogsfrogs> (raw)

Hi Chandan,

Please pull this branch with changes for xfs for 6.7-rc1.

As usual, I did a test-merge with the main upstream branch as of a few
minutes ago, and didn't see any conflicts.  Please let me know if you
encounter any problems.

--D

The following changes since commit c2988eb5cff75c02bc57e02c323154aa08f55b78:

xfs: rt stubs should return negative errnos when rt disabled (2023-10-17 16:22:40 -0700)

are available in the Git repository at:

https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git tags/clean-up-realtime-units-6.7_2023-10-19

for you to fetch changes up to 2d5f216b77e33f9b503bd42998271da35d4b7055:

xfs: convert rt extent numbers to xfs_rtxnum_t (2023-10-17 16:24:22 -0700)

----------------------------------------------------------------
xfs: clean up realtime type usage [v1.1]

The realtime code uses xfs_rtblock_t and xfs_fsblock_t in a lot of
places, and it's very confusing.  Clean up all the type usage so that an
xfs_rtblock_t is always a block within the realtime volume, an
xfs_fileoff_t is always a file offset within a realtime metadata file,
and an xfs_rtxnumber_t is always a rt extent within the realtime volume.

v1.1: various cleanups suggested by hch

With a bit of luck, this should all go splendidly.

Signed-off-by: Darrick J. Wong <djwong@kernel.org>

----------------------------------------------------------------
Darrick J. Wong (8):
xfs: fix units conversion error in xfs_bmap_del_extent_delay
xfs: make sure maxlen is still congruent with prod when rounding down
xfs: move the xfs_rtbitmap.c declarations to xfs_rtbitmap.h
xfs: convert xfs_extlen_t to xfs_rtxlen_t in the rt allocator
xfs: convert rt bitmap/summary block numbers to xfs_fileoff_t
xfs: convert rt bitmap extent lengths to xfs_rtbxlen_t
xfs: rename xfs_verify_rtext to xfs_verify_rtbext
xfs: convert rt extent numbers to xfs_rtxnum_t

fs/xfs/libxfs/xfs_bmap.c     |   8 +-
fs/xfs/libxfs/xfs_format.h   |   2 +-
fs/xfs/libxfs/xfs_rtbitmap.c | 121 ++++++++++-----------
fs/xfs/libxfs/xfs_rtbitmap.h |  79 ++++++++++++++
fs/xfs/libxfs/xfs_types.c    |   4 +-
fs/xfs/libxfs/xfs_types.h    |   8 +-
fs/xfs/scrub/bmap.c          |   2 +-
fs/xfs/scrub/fscounters.c    |   2 +-
fs/xfs/scrub/rtbitmap.c      |  12 +--
fs/xfs/scrub/rtsummary.c     |   4 +-
fs/xfs/scrub/trace.h         |   7 +-
fs/xfs/xfs_bmap_util.c       |  18 ++--
fs/xfs/xfs_fsmap.c           |   2 +-
fs/xfs/xfs_rtalloc.c         | 248 +++++++++++++++++++++++--------------------
fs/xfs/xfs_rtalloc.h         |  89 ++--------------
15 files changed, 319 insertions(+), 287 deletions(-)
create mode 100644 fs/xfs/libxfs/xfs_rtbitmap.h

                 reply	other threads:[~2023-10-20 22:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=169781767994.780878.672267596860381813.stg-ugh@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=chandanbabu@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-xfs@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.