public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Wengang Wang <wen.gang.wang@oracle.com>
To: linux-xfs@vger.kernel.org
Cc: wen.gang.wang@oracle.com
Subject: [PATCH 0/2] xfs: one extent per EFI
Date: Fri, 14 Apr 2023 15:58:34 -0700	[thread overview]
Message-ID: <20230414225836.8952-1-wen.gang.wang@oracle.com> (raw)

We are hitting the deadlock described in patch 1.
This patchset doesn't want to disturb the existing block allocation
routine, that would make the allocation routime even complex. Instead,
this patch avoids doing AGFL block allocation holding busy extents in current
memory transaction.

Patch 1 fixes the IO path and Patch 2 takes care of log recovery.

Wengang Wang (2):
  xfs: IO time one extent per EFI
  xfs: log recovery stage split EFIs with multiple extents

 fs/xfs/xfs_extfree_item.c | 104 ++++++++++++++++++++++++++++++++++----
 fs/xfs/xfs_extfree_item.h |   9 +++-
 2 files changed, 101 insertions(+), 12 deletions(-)

-- 
2.21.0 (Apple Git-122.2)


             reply	other threads:[~2023-04-14 22:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 22:58 Wengang Wang [this message]
2023-04-14 22:58 ` [PATCH 1/2] xfs: IO time one extent per EFI Wengang Wang
2023-04-19 23:55   ` Dave Chinner
2023-04-20 17:31     ` Wengang Wang
2023-04-20 23:22       ` Dave Chinner
2023-04-21  0:24         ` Wengang Wang
2023-04-21  9:34           ` Dave Chinner
2023-04-21 18:23             ` Wengang Wang
2023-04-22  3:22               ` Wengang Wang
2023-04-24 15:53                 ` Wengang Wang
2023-04-24 22:52                   ` Wengang Wang
2023-04-14 22:58 ` [PATCH 2/2] xfs: log recovery stage split EFIs with multiple extents Wengang Wang
2023-04-20  0:30   ` Dave Chinner
2023-04-20 17:10     ` Wengang Wang
2023-04-20 22:54       ` Dave Chinner
2023-04-21  0:32         ` Wengang Wang

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=20230414225836.8952-1-wen.gang.wang@oracle.com \
    --to=wen.gang.wang@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox