All of lore.kernel.org
 help / color / mirror / Atom feed
From: cem@kernel.org
To: linux-xfs@vger.kernel.org
Cc: david@fromorbit.com, hch@lst.de, djwong@kernel.org
Subject: [PATCH 0/3] Decouple busy_extents from cil context
Date: Tue, 10 Mar 2026 13:33:13 +0100	[thread overview]
Message-ID: <20260310123324.339310-1-cem@kernel.org> (raw)

From: Carlos Maiolino <cem@kernel.org>

This series belongs to some work I am doing on AIL aiming to improve its
writeback performance.

I need the cil context to be treated as a single unit during AIL
processing, and having busy_extents associated with it gets in the way.

This has passed the same tests I run during patch integration without
regressions.

Instead of keeping rebasing it on top of newer versions, I'd appreciate
I could get reviews and upstream this part now, to reduce the amount of
changes I need to rebase.

I should get the next part ready soon once I fix a few issues on it.

Carlos Maiolino (3):
  xfs: add a couple helpers to alloc/free xfs_busy_extents
  xfs: convert busy_extents list to a pointer within cil context
  xfs: remove owner field from xfs_extent_busy

 fs/xfs/xfs_discard.c     | 17 ++++++-----------
 fs/xfs/xfs_extent_busy.h | 24 +++++++++++++++++-------
 fs/xfs/xfs_log_cil.c     | 18 ++++++++----------
 fs/xfs/xfs_log_priv.h    |  2 +-
 4 files changed, 32 insertions(+), 29 deletions(-)

Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
-- 
2.53.0


             reply	other threads:[~2026-03-10 12:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10 12:33 cem [this message]
2026-03-10 12:33 ` [PATCH 1/3] xfs: add a couple helpers to alloc/free xfs_busy_extents cem
2026-03-10 13:03   ` Christoph Hellwig
2026-03-10 12:33 ` [PATCH 2/3] xfs: convert busy_extents list to a pointer within cil context cem
2026-03-10 13:04   ` Christoph Hellwig
2026-03-10 12:33 ` [PATCH 3/3] xfs: remove owner field from xfs_extent_busy cem
2026-03-10 13:06   ` Christoph Hellwig

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=20260310123324.339310-1-cem@kernel.org \
    --to=cem@kernel.org \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --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 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.