public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs: process free extents to busy list in FIFO order
Date: Tue, 10 Oct 2023 10:34:04 -0700	[thread overview]
Message-ID: <20231010173404.GF21298@frogsfrogsfrogs> (raw)
In-Reply-To: <ZST1oEZlh6/UAQwS@infradead.org>

On Mon, Oct 09, 2023 at 11:56:32PM -0700, Christoph Hellwig wrote:
> On Mon, Oct 09, 2023 at 11:25:56AM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> > 
> > When we're adding extents to the busy discard list, add them to the tail
> > of the list so that we get FIFO order.  For FITRIM commands, this means
> > that we send discard bios sorted in order from longest to shortest, like
> > we did before commit 89cfa899608fc.
> > 
> > For transactions that are freeing extents, this puts them in the
> > transaction's busy list in FIFO order as well, which shouldn't make any
> > noticeable difference.
> > 
> > Fixes: 89cfa899608fc ("xfs: reduce AGF hold times during fstrim operations")
> > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> 
> Does this actually fix an observed issue, or just restor the previous
> behavior?

I don't /think/ there's a real issue here; it just looks funny that the
tracepoints are now ordered from higher to lower LBAs within arbitrarily
sized groups.

--D

> Eitherway the change make sense:
> 
> Reviewed-by: Christoph Hellwig <hch@lst.de>

      reply	other threads:[~2023-10-10 17:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09 18:25 [PATCHSET 0/2] xfs: bug fixes for 6.6 Darrick J. Wong
2023-10-09 18:25 ` [PATCH 1/2] xfs: adjust the incore perag block_count when shrinking Darrick J. Wong
2023-10-10  6:55   ` Christoph Hellwig
2023-10-09 18:25 ` [PATCH 2/2] xfs: process free extents to busy list in FIFO order Darrick J. Wong
2023-10-10  6:56   ` Christoph Hellwig
2023-10-10 17:34     ` 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=20231010173404.GF21298@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox