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 4/6] xfs: refactor rtbitmap/summary macros
Date: Fri, 20 Oct 2023 15:17:45 -0700	[thread overview]
Message-ID: <169781768181.780878.1129014342842627388.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 ef5a83b7e597038d1c734ddb4bc00638082c2bf1:

xfs: use shifting and masking when converting rt extents, if possible (2023-10-17 16:26:25 -0700)

are available in the Git repository at:

https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git tags/refactor-rtbitmap-macros-6.7_2023-10-19

for you to fetch changes up to d0448fe76ac1a9ccbce574577a4c82246d17eec4:

xfs: create helpers for rtbitmap block/wordcount computations (2023-10-18 10:58:58 -0700)

----------------------------------------------------------------
xfs: refactor rtbitmap/summary macros [v1.1]

In preparation for adding block headers and enforcing endian order in
rtbitmap and rtsummary blocks, replace open-coded geometry computations
and fugly macros with proper helper functions that can be typechecked.
Soon we'll be needing to add more complex logic to the helpers.

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 (5):
xfs: convert the rtbitmap block and bit macros to static inline functions
xfs: remove XFS_BLOCKWSIZE and XFS_BLOCKWMASK macros
xfs: convert open-coded xfs_rtword_t pointer accesses to helper
xfs: convert rt summary macros to helpers
xfs: create helpers for rtbitmap block/wordcount computations

fs/xfs/libxfs/xfs_format.h     |  16 +----
fs/xfs/libxfs/xfs_rtbitmap.c   | 142 +++++++++++++++++++++++++----------------
fs/xfs/libxfs/xfs_rtbitmap.h   | 100 +++++++++++++++++++++++++++++
fs/xfs/libxfs/xfs_trans_resv.c |   9 +--
fs/xfs/libxfs/xfs_types.h      |   2 +
fs/xfs/scrub/rtsummary.c       |  23 +++----
fs/xfs/xfs_rtalloc.c           |  22 +++----
7 files changed, 218 insertions(+), 96 deletions(-)

                 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=169781768181.780878.1129014342842627388.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.