Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 00/14] xfs: perag conversions for 5.20
Date: Wed, 29 Jun 2022 13:26:35 -0700	[thread overview]
Message-ID: <Yry1ez1e4a11l3Yk@magnolia> (raw)
In-Reply-To: <20220627001832.215779-1-david@fromorbit.com>

On Mon, Jun 27, 2022 at 10:18:18AM +1000, Dave Chinner wrote:
> Hi folks,
> 
> This is the set of per-ag conversions that I'm proposing for the
> 5.20 cycle. It is the initial subset of changes that were listed in
> the larger "upcoming perag changes for shrink" patchset here:
> 
> https://lore.kernel.org/linux-xfs/20220611012659.3418072-1-david@fromorbit.com/
> 
> This series drives the perag down into the AGI, AGF and AGFL access
> routines and unifies the perag structure initialisation with the
> high level AG header read functions. This largely replaces the
> xfs_mount/agno pair that is passed to all these functions with a
> perag, and in most places we already have a perag ready to pass in.
> There are a few places where perags need to be grabbed before
> reading the AG header buffers - some of these will need to be driven
> to higher layers to ensure we can run operations on AGs without
> getting stuck part way through waiting on a perag reference.
> 
> The latter section of this patchset moves some of the AG geometry
> information from the xfs_mount to the xfs_perag, and starts
> converting code that requires geometry validation to use a perag
> instead of a mount and having to extract the AGNO from the object
> location. This also allows us to store the AG size in the perag and
> then we can stop having to compare the agno against sb_agcount to
> determine if the AG is the last AG and so has a runt size.  This
> greatly simplifies some of the type validity checking we do and
> substantially reduces the CPU overhead of type validity checking. It
> also cuts over 1.2kB out of the binary size.
> 
> This runs through fstests cleanly - I don't expect there to be
> hidden surprises in it so I think these patches are good to go
> for the 5.20 cycle.
> 
> Comments and thoughts welcome....

The entire series LGTM
Reviewed-by: Darrick J. Wong <djwong@kernel.org>

--D

> 
> -Dave.
> 
> 

      parent reply	other threads:[~2022-06-29 20:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27  0:18 [PATCH 00/14] xfs: perag conversions for 5.20 Dave Chinner
2022-06-27  0:18 ` [PATCH 01/14] xfs: make last AG grow/shrink perag centric Dave Chinner
2022-06-27  0:18 ` [PATCH 02/14] xfs: kill xfs_ialloc_pagi_init() Dave Chinner
2022-06-27  0:18 ` [PATCH 03/14] xfs: pass perag to xfs_ialloc_read_agi() Dave Chinner
2022-06-27  0:18 ` [PATCH 04/14] xfs: kill xfs_alloc_pagf_init() Dave Chinner
2022-06-27  0:18 ` [PATCH 05/14] xfs: pass perag to xfs_alloc_read_agf() Dave Chinner
2022-06-29  6:58   ` Christoph Hellwig
2022-06-27  0:18 ` [PATCH 06/14] xfs: pass perag to xfs_read_agi Dave Chinner
2022-06-27  0:18 ` [PATCH 07/14] xfs: pass perag to xfs_read_agf Dave Chinner
2022-06-27  0:18 ` [PATCH 08/14] xfs: pass perag to xfs_alloc_get_freelist Dave Chinner
2022-06-27  0:18 ` [PATCH 09/14] xfs: pass perag to xfs_alloc_put_freelist Dave Chinner
2022-06-27  0:18 ` [PATCH 10/14] xfs: pass perag to xfs_alloc_read_agfl Dave Chinner
2022-06-27  0:18 ` [PATCH 11/14] xfs: Pre-calculate per-AG agbno geometry Dave Chinner
2022-06-29  7:00   ` Christoph Hellwig
2022-06-27  0:18 ` [PATCH 12/14] xfs: Pre-calculate per-AG agino geometry Dave Chinner
2022-06-29  7:02   ` Christoph Hellwig
2022-06-27  0:18 ` [PATCH 13/14] xfs: replace xfs_ag_block_count() with perag accesses Dave Chinner
2022-06-29  7:02   ` Christoph Hellwig
2022-06-27  0:18 ` [PATCH 14/14] xfs: make is_log_ag() a first class helper Dave Chinner
2022-06-29  7:03   ` Christoph Hellwig
2022-06-29 20:26 ` Darrick J. Wong [this message]

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=Yry1ez1e4a11l3Yk@magnolia \
    --to=djwong@kernel.org \
    --cc=david@fromorbit.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox