All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH 0/2] xfs: a couple misc/small deferred inactivation tweaks
Date: Thu, 13 Jan 2022 08:36:59 -0500	[thread overview]
Message-ID: <20220113133701.629593-1-bfoster@redhat.com> (raw)

Hi all,

This is just a couple small gc tweaks associated with deferred
inactivation. Patch 1 is intended to be a fix for a race described in
the commit log description. I think it's equivalent to the intent of the
current code, but could be mistaken. Patch 2 is intended to be a
usability improvement around freeze vs. inode reclaim given the new
behavior of the latter wrt deferred inactivation. Full disclosure: the
idea of patch 2 has previously shown to be contentious. My view is this
is a simple and incremental improvement over current upstream behavior,
so I'm posting it regardless. Feel free to drop it in favor of existing
behavior or something else.

Brian

Brian Foster (2):
  xfs: flush inodegc workqueue tasks before cancel
  xfs: run blockgc on freeze to avoid iget stalls after reclaim

 fs/xfs/xfs_icache.c | 22 ++++------------------
 fs/xfs/xfs_super.c  | 19 +++++++++++++++++--
 2 files changed, 21 insertions(+), 20 deletions(-)

-- 
2.31.1


             reply	other threads:[~2022-01-13 13:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 13:36 Brian Foster [this message]
2022-01-13 13:37 ` [PATCH 1/2] xfs: flush inodegc workqueue tasks before cancel Brian Foster
2022-01-13 18:35   ` Darrick J. Wong
2022-01-13 22:19   ` Dave Chinner
2022-01-13 13:37 ` [PATCH 2/2] xfs: run blockgc on freeze to avoid iget stalls after reclaim Brian Foster
2022-01-13 17:13   ` Darrick J. Wong
2022-01-13 19:58     ` Brian Foster
2022-01-13 20:43       ` Darrick J. Wong
2022-01-13 21:01         ` Darrick J. Wong
2022-01-13 22:38   ` Dave Chinner
2022-01-14 17:35     ` Darrick J. Wong
2022-01-14 19:45       ` Brian Foster
2022-01-14 21:30         ` Darrick J. Wong
2022-01-15  4:09           ` Darrick J. Wong
2022-01-15 22:40           ` Dave Chinner
2022-01-17 13:37           ` Brian Foster
2022-01-18 18:56             ` Darrick J. Wong
2022-01-19 20:07               ` Brian Foster
2022-01-20  0:36                 ` Darrick J. Wong
2022-01-20  5:18                   ` Dave Chinner
2022-01-24 16:57                   ` Brian Foster
2022-02-02  2:22                     ` Dave Chinner
2022-02-10 19:03                       ` Brian Foster
2022-02-10 23:08                         ` Dave Chinner
2022-02-15  1:54                           ` Darrick J. Wong
2022-02-15  9:26                             ` Dave Chinner

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=20220113133701.629593-1-bfoster@redhat.com \
    --to=bfoster@redhat.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 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.