From: Brian Foster <bfoster@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-xfs@vger.kernel.org, eguan@redhat.com, darrick.wong@oracle.com
Subject: Re: [PATCH 5/5] xfs: don't rely on ->total in xfs_alloc_space_available
Date: Wed, 4 Jan 2017 13:19:47 -0500 [thread overview]
Message-ID: <20170104181947.GE41989@bfoster.bfoster> (raw)
In-Reply-To: <1482436822-31546-6-git-send-email-hch@lst.de>
On Thu, Dec 22, 2016 at 09:00:22PM +0100, Christoph Hellwig wrote:
> ->total is a bit of an odd parameter passed down to the low-level
> allocator all the way from the high-level callers. It's supposed to
> contain the maximum number of blocks to be allocated for the whole
> transaction [1].
>
> But in xfs_iomap_write_allocate we only convert existing delayed
> allocations and thus only have a minimal block reservation for the
> current transaction, so xfs_alloc_space_available can't use it for
> the allocation decisions. Use the maximum of args->total and the
> calculated block requirement to make a decision. We probably should
> get rid of args->total eventually and instead apply ->minleft more
> broadly, but that will require some extensive changes all over.
>
> [1] which creates lots of confusion as most callers don't decrement it
> once doing a first allocation. But that's for a separate series.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
Reviewed-by: Brian Foster <bfoster@redhat.com>
> fs/xfs/libxfs/xfs_alloc.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_alloc.c b/fs/xfs/libxfs/xfs_alloc.c
> index 6a10aab..c121407 100644
> --- a/fs/xfs/libxfs/xfs_alloc.c
> +++ b/fs/xfs/libxfs/xfs_alloc.c
> @@ -1995,7 +1995,7 @@ xfs_alloc_space_available(
> int flags)
> {
> struct xfs_perag *pag = args->pag;
> - xfs_extlen_t longest;
> + xfs_extlen_t alloc_len, longest;
> xfs_extlen_t reservation; /* blocks that are still reserved */
> int available;
>
> @@ -2005,15 +2005,16 @@ xfs_alloc_space_available(
> reservation = xfs_ag_resv_needed(pag, args->resv);
>
> /* do we have enough contiguous free space for the allocation? */
> + alloc_len = args->minlen + (args->alignment - 1) + args->minalignslop;
> longest = xfs_alloc_longest_free_extent(args->mp, pag, min_free,
> reservation);
> - if ((args->minlen + args->alignment + args->minalignslop - 1) > longest)
> + if (longest < alloc_len)
> return false;
>
> /* do we have enough free space remaining for the allocation? */
> available = (int)(pag->pagf_freeblks + pag->pagf_flcount -
> reservation - min_free - args->minleft);
> - if (available < (int)args->total)
> + if (available < (int)max(args->total, alloc_len))
> return false;
>
> /*
> --
> 2.1.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-01-04 18:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 20:00 minleft fixes V2 Christoph Hellwig
2016-12-22 20:00 ` [PATCH 1/5] xfs: bump up reserved blocks in xfs_alloc_set_aside Christoph Hellwig
2017-01-04 14:33 ` Brian Foster
2017-01-08 10:30 ` Christoph Hellwig
2017-01-08 16:07 ` Brian Foster
2016-12-22 20:00 ` [PATCH 2/5] xfs: fix the alignment fallback in xfs_bmap_btalloc Christoph Hellwig
2017-01-04 14:34 ` Brian Foster
2017-01-08 10:31 ` Christoph Hellwig
2017-01-08 16:08 ` Brian Foster
2016-12-22 20:00 ` [PATCH 3/5] xfs: fix bogus minleft manipulations Christoph Hellwig
2017-01-04 18:19 ` Brian Foster
2017-01-08 10:36 ` Christoph Hellwig
2017-01-08 16:09 ` Brian Foster
2017-01-09 17:56 ` Christoph Hellwig
2016-12-22 20:00 ` [PATCH 4/5] xfs: adjust allocation length in xfs_alloc_space_available Christoph Hellwig
2017-01-04 18:19 ` Brian Foster
2016-12-22 20:00 ` [PATCH 5/5] xfs: don't rely on ->total " Christoph Hellwig
2017-01-04 18:19 ` Brian Foster [this message]
2017-01-05 1:21 ` minleft fixes V2 Eryu Guan
2017-01-05 2:01 ` Darrick J. Wong
2017-01-08 10:36 ` Christoph Hellwig
2017-01-08 16:10 ` Brian Foster
2017-01-08 18:10 ` Darrick J. Wong
2017-01-09 15:22 ` Brian Foster
2017-01-09 15:34 ` Christoph Hellwig
2017-01-09 15:43 ` Brian Foster
2017-01-10 4:23 ` Darrick J. Wong
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=20170104181947.GE41989@bfoster.bfoster \
--to=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=eguan@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox