All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-xfs@vger.kernel.org, hch@infradead.org
Subject: Re: [PATCH 2/4] xfs: measure all contiguous previous extents for prealloc size
Date: Fri, 22 May 2020 17:27:41 -0700	[thread overview]
Message-ID: <20200523002741.GD8230@magnolia> (raw)
In-Reply-To: <20200522112722.GA50656@bfoster>

On Fri, May 22, 2020 at 07:27:22AM -0400, Brian Foster wrote:
> On Thu, May 21, 2020 at 07:53:09PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> > 
> > When we're estimating a new speculative preallocation length for an
> > extending write, we should walk backwards through the extent list to
> > determine the number of number of blocks that are physically and
> > logically contiguous with the write offset, and use that as an input to
> > the preallocation size computation.
> > 
> > This way, preallocation length is truly measured by the effectiveness of
> > the allocator in giving us contiguous allocations without being
> > influenced by the state of a given extent.  This fixes both the problem
> > where ZERO_RANGE within an EOF can reduce preallocation, and prevents
> > the unnecessary shrinkage of preallocation when delalloc extents are
> > turned into unwritten extents.
> > 
> > This was found as a regression in xfs/014 after changing delalloc writes
> > to create unwritten extents during writeback.
> > 
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> > ---
> >  fs/xfs/xfs_iomap.c |   37 +++++++++++++++++++++++++------------
> >  1 file changed, 25 insertions(+), 12 deletions(-)
> > 
> > 
> > diff --git a/fs/xfs/xfs_iomap.c b/fs/xfs/xfs_iomap.c
> > index ac970b13b1f8..6a308af93893 100644
> > --- a/fs/xfs/xfs_iomap.c
> > +++ b/fs/xfs/xfs_iomap.c
> > @@ -377,15 +377,17 @@ xfs_iomap_prealloc_size(
> >  	loff_t			count,
> >  	struct xfs_iext_cursor	*icur)
> >  {
> > +	struct xfs_iext_cursor	ncur = *icur; /* struct copy */
> > +	struct xfs_bmbt_irec	prev, got;
> >  	struct xfs_mount	*mp = ip->i_mount;
> >  	struct xfs_ifork	*ifp = XFS_IFORK_PTR(ip, whichfork);
> >  	xfs_fileoff_t		offset_fsb = XFS_B_TO_FSBT(mp, offset);
> > -	struct xfs_bmbt_irec	prev;
> > -	int			shift = 0;
> >  	int64_t			freesp;
> >  	xfs_fsblock_t		qblocks;
> > -	int			qshift = 0;
> >  	xfs_fsblock_t		alloc_blocks = 0;
> > +	xfs_extlen_t		plen;
> > +	int			shift = 0;
> > +	int			qshift = 0;
> >  
> >  	if (offset + count <= XFS_ISIZE(ip))
> >  		return 0;
> > @@ -413,16 +415,27 @@ xfs_iomap_prealloc_size(
> >  	 * preallocation size.
> >  	 *
> >  	 * If the extent is a hole, then preallocation is essentially disabled.
> > -	 * Otherwise we take the size of the preceding data extent as the basis
> > -	 * for the preallocation size. If the size of the extent is greater than
> > -	 * half the maximum extent length, then use the current offset as the
> > -	 * basis. This ensures that for large files the preallocation size
> > -	 * always extends to MAXEXTLEN rather than falling short due to things
> > -	 * like stripe unit/width alignment of real extents.
> > +	 * Otherwise we take the size of the preceding data extents as the basis
> > +	 * for the preallocation size. Note that we don't care if the previous
> > +	 * extents are written or not.
> > +	 *
> > +	 * If the size of the extents is greater than half the maximum extent
> > +	 * length, then use the current offset as the basis. This ensures that
> > +	 * for large files the preallocation size always extends to MAXEXTLEN
> > +	 * rather than falling short due to things like stripe unit/width
> > +	 * alignment of real extents.
> >  	 */
> > -	if (prev.br_blockcount <= (MAXEXTLEN >> 1))
> > -		alloc_blocks = prev.br_blockcount << 1;
> > -	else
> > +	plen = prev.br_blockcount;
> 
> If prev is initialized by peeking the previous extent, then it looks
> like the first iteration of this loop compares the immediately previous
> extent with itself..

D'oh.  I misported that when I was munging patches around.  Since we
copy *icur to ncur, we can replace the previous peek against icur with a
call to xfs_iext_prev_extent on ncur.

> > +	while (xfs_iext_prev_extent(ifp, &ncur, &got)) {
> > +		if (plen > MAXEXTLEN / 2 ||
> > +		    got.br_startoff + got.br_blockcount != prev.br_startoff ||
> > +		    got.br_startblock + got.br_blockcount != prev.br_startblock)
> 
> We should probably check for nullstartblock (delalloc) extents
> explicitly here rather than rely on the calculation to fail.

Ok.

> > +			break;
> > +		plen += got.br_blockcount;
> 
> 
> 
> > +		prev = got;
> > +	}
> > +	alloc_blocks = plen * 2;
> 
> Why do we replace the bit shifts with division/multiplication? I'd
> prefer to see the former for obvious power of 2 operations, even if this
> happens to be 32-bit arithmetic. I don't see any particular reason to
> change it in this patch.

Fair enough.  Thanks for catching those things.

--D

> Brian
> 
> > +	if (alloc_blocks > MAXEXTLEN)
> >  		alloc_blocks = XFS_B_TO_FSB(mp, offset);
> >  	if (!alloc_blocks)
> >  		goto check_writeio;
> > 
> 

  reply	other threads:[~2020-05-23  0:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22  2:52 [PATCH v3 0/4] xfs: fix stale disk exposure after crash Darrick J. Wong
2020-05-22  2:53 ` [PATCH 1/4] xfs: don't fail unwritten extent conversion on writeback due to edquot Darrick J. Wong
2020-05-22  2:53 ` [PATCH 2/4] xfs: measure all contiguous previous extents for prealloc size Darrick J. Wong
2020-05-22  6:56   ` Christoph Hellwig
2020-05-23  0:25     ` Darrick J. Wong
2020-05-22 11:27   ` Brian Foster
2020-05-23  0:27     ` Darrick J. Wong [this message]
2020-05-23  7:09     ` Christoph Hellwig
2020-05-22  2:53 ` [PATCH 3/4] xfs: refactor xfs_iomap_prealloc_size Darrick J. Wong
2020-05-22  6:57   ` Christoph Hellwig
2020-05-22  2:53 ` [PATCH 4/4] xfs: force writes to delalloc regions to unwritten Darrick J. Wong
2020-05-22  3:31   ` Dave Chinner
2020-05-22  3:56     ` Darrick J. Wong
  -- strict thread matches above, loose matches on Subject: below --
2020-05-23 16:49 [PATCH v4 0/4] xfs: fix stale disk exposure after crash Darrick J. Wong
2020-05-23 16:49 ` [PATCH 2/4] xfs: measure all contiguous previous extents for prealloc size Darrick J. Wong
2020-05-24  9:14   ` Christoph Hellwig
2020-05-24 17:16     ` 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=20200523002741.GD8230@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=bfoster@redhat.com \
    --cc=hch@infradead.org \
    --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.