From: "Darrick J. Wong" <djwong@kernel.org>
To: John Garry <john.g.garry@oracle.com>
Cc: chandan.babu@oracle.com, dchinner@redhat.com, hch@lst.de,
viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, catherine.hoang@oracle.com,
martin.petersen@oracle.com
Subject: Re: [PATCH 06/13] xfs: align args->minlen for forced allocation alignment
Date: Fri, 21 Jun 2024 13:38:06 -0700 [thread overview]
Message-ID: <20240621203806.GW3058325@frogsfrogsfrogs> (raw)
In-Reply-To: <20240621100540.2976618-7-john.g.garry@oracle.com>
On Fri, Jun 21, 2024 at 10:05:33AM +0000, John Garry wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> If args->minlen is not aligned to the constraints of forced
> alignment, we may do minlen allocations that are not aligned when we
> approach ENOSPC. Avoid this by always aligning args->minlen
> appropriately. If alignment of minlen results in a value smaller
> than the alignment constraint, fail the allocation immediately.
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> Signed-off-by: John Garry <john.g.garry@oracle.com>
Looks good!
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> fs/xfs/libxfs/xfs_bmap.c | 45 +++++++++++++++++++++++++++-------------
> 1 file changed, 31 insertions(+), 14 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_bmap.c b/fs/xfs/libxfs/xfs_bmap.c
> index 9131ba8113a6..c9cf138e13c4 100644
> --- a/fs/xfs/libxfs/xfs_bmap.c
> +++ b/fs/xfs/libxfs/xfs_bmap.c
> @@ -3278,33 +3278,48 @@ xfs_bmap_longest_free_extent(
> return 0;
> }
>
> -static xfs_extlen_t
> +static int
> xfs_bmap_select_minlen(
> struct xfs_bmalloca *ap,
> struct xfs_alloc_arg *args,
> xfs_extlen_t blen)
> {
> -
> /* Adjust best length for extent start alignment. */
> if (blen > args->alignment)
> blen -= args->alignment;
>
> /*
> * Since we used XFS_ALLOC_FLAG_TRYLOCK in _longest_free_extent(), it is
> - * possible that there is enough contiguous free space for this request.
> + * possible that there is enough contiguous free space for this request
> + * even if best length is less that the minimum length we need.
> + *
> + * If the best length won't satisfy the maximum length we requested,
> + * then use it as the minimum length so we get as large an allocation
> + * as possible.
> */
> if (blen < ap->minlen)
> - return ap->minlen;
> + blen = ap->minlen;
> + else if (blen > args->maxlen)
> + blen = args->maxlen;
>
> /*
> - * If the best seen length is less than the request length,
> - * use the best as the minimum, otherwise we've got the maxlen we
> - * were asked for.
> + * If we have alignment constraints, round the minlen down to match the
> + * constraint so that alignment will be attempted. This may reduce the
> + * allocation to smaller than was requested, so clamp the minimum to
> + * ap->minlen to allow unaligned allocation to succeed. If we are forced
> + * to align the allocation, return ENOSPC at this point because we don't
> + * have enough contiguous free space to guarantee aligned allocation.
> */
> - if (blen < args->maxlen)
> - return blen;
> - return args->maxlen;
> -
> + if (args->alignment > 1) {
> + blen = rounddown(blen, args->alignment);
> + if (blen < ap->minlen) {
> + if (args->datatype & XFS_ALLOC_FORCEALIGN)
> + return -ENOSPC;
> + blen = ap->minlen;
> + }
> + }
> + args->minlen = blen;
> + return 0;
> }
>
> static int
> @@ -3340,8 +3355,7 @@ xfs_bmap_btalloc_select_lengths(
> if (pag)
> xfs_perag_rele(pag);
>
> - args->minlen = xfs_bmap_select_minlen(ap, args, blen);
> - return error;
> + return xfs_bmap_select_minlen(ap, args, blen);
> }
>
> /* Update all inode and quota accounting for the allocation we just did. */
> @@ -3661,7 +3675,10 @@ xfs_bmap_btalloc_filestreams(
> goto out_low_space;
> }
>
> - args->minlen = xfs_bmap_select_minlen(ap, args, blen);
> + error = xfs_bmap_select_minlen(ap, args, blen);
> + if (error)
> + goto out_low_space;
> +
> if (ap->aeof && ap->offset)
> error = xfs_bmap_btalloc_at_eof(ap, args);
>
> --
> 2.31.1
>
>
next prev parent reply other threads:[~2024-06-21 20:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 10:05 [PATCH 00/13] forcealign for xfs John Garry
2024-06-21 10:05 ` [PATCH 01/13] xfs: only allow minlen allocations when near ENOSPC John Garry
2024-06-21 19:42 ` Darrick J. Wong
2024-06-21 20:04 ` Darrick J. Wong
2024-06-21 10:05 ` [PATCH 02/13] xfs: always tail align maxlen allocations John Garry
2024-06-21 19:50 ` Darrick J. Wong
2024-06-21 10:05 ` [PATCH 03/13] xfs: simplify extent allocation alignment John Garry
2024-06-21 20:29 ` Darrick J. Wong
2024-06-21 10:05 ` [PATCH 04/13] xfs: make EOF allocation simpler John Garry
2024-06-21 20:35 ` Darrick J. Wong
2024-06-21 10:05 ` [PATCH 05/13] xfs: introduce forced allocation alignment John Garry
2024-06-21 20:37 ` Darrick J. Wong
2024-06-21 10:05 ` [PATCH 06/13] xfs: align args->minlen for " John Garry
2024-06-21 20:38 ` Darrick J. Wong [this message]
2024-06-21 10:05 ` [PATCH 07/13] xfs: Introduce FORCEALIGN inode flag John Garry
2024-06-21 19:07 ` Darrick J. Wong
2024-06-24 14:36 ` John Garry
2024-06-21 10:05 ` [PATCH 08/13] xfs: Do not free EOF blocks for forcealign John Garry
2024-06-21 19:08 ` Darrick J. Wong
2024-06-24 15:04 ` John Garry
2024-06-21 10:05 ` [PATCH 09/13] xfs: Update xfs_inode_alloc_unitsize_fsb() " John Garry
2024-06-21 18:38 ` Darrick J. Wong
2024-06-24 7:34 ` John Garry
2024-06-21 10:05 ` [PATCH 10/13] xfs: Unmap blocks according to forcealign John Garry
2024-06-21 19:12 ` Darrick J. Wong
2024-06-24 15:12 ` John Garry
2024-06-21 10:05 ` [PATCH 11/13] xfs: Only free full extents for forcealign John Garry
2024-06-21 19:13 ` Darrick J. Wong
2024-06-21 10:05 ` [PATCH 12/13] xfs: Don't revert allocated offset " John Garry
2024-06-21 19:13 ` Darrick J. Wong
2024-06-21 10:05 ` [PATCH 13/13] xfs: Enable file data forcealign feature John Garry
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=20240621203806.GW3058325@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=brauner@kernel.org \
--cc=catherine.hoang@oracle.com \
--cc=chandan.babu@oracle.com \
--cc=dchinner@redhat.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=john.g.garry@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).