Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Carlos Maiolino <cem@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: "Darrick J. Wong" <djwong@kernel.org>, linux-xfs@vger.kernel.org
Subject: Re: misc buffer cache improvements
Date: Mon, 10 Aug 2026 13:55:33 +0200	[thread overview]
Message-ID: <178636293365.58486.12109129017004452043.b4-ty@kernel.org> (raw)
In-Reply-To: <20260715145147.95654-1-hch@lst.de>

On Wed, 15 Jul 2026 16:50:53 +0200, Christoph Hellwig wrote:
> a bunch of misc xfs_buf patches.  These came out of a little
> project that needs a async read API (not actually included here),
> and to get there a lot of lose ends had to be cleaned up, and a
> lockless path for readaheads that doesn't kick off the read fell
> out easily.
> 
> Diffstat:
>  libxfs/xfs_btree_staging.c |    7
>  libxfs/xfs_dquot_buf.c     |    8
>  libxfs/xfs_ialloc.c        |    2
>  libxfs/xfs_inode_buf.c     |   15 -
>  xfs_buf.c                  |  392 +++++++++++++++++++++++----------------------
>  xfs_buf.h                  |    8
>  xfs_buf_item.c             |   10 -
>  xfs_buf_item_recover.c     |    3
>  xfs_dquot_item_recover.c   |    1
>  xfs_fsops.c                |    2
>  xfs_inode.c                |    4
>  xfs_inode_item_recover.c   |    1
>  xfs_log_recover.c          |    5
>  xfs_trace.h                |    2
>  xfs_trans_buf.c            |    7
>  15 files changed, 239 insertions(+), 228 deletions(-)
> 
> [...]

Applied to for-next, thanks!

[01/12] xfs: don't get a pag reference in xfs_buf_get_map
        commit: 45fd506c334ceb79ea3b40986b2c5ebb7802b385
[02/12] xfs: consolidate buffer locking in xfs_buf_get_map
        commit: 568c8798a3d0afabc133d7b34d37155daa95d1f2
[03/12] xfs: split out a lower-level xfs_buf_get_map helper from xfs_find_get_buf
        commit: b6ba780af010f0d1c5bfb970fe692a02559de473
[04/12] xfs: remove spurious XBF_DONE clearing on readahead validation failure
        commit: 7a4eae80b5b3db8d68961af3707fd56f2220cc29
[05/12] xfs: remove _XBF_LOGRECOVERY
        commit: d80fe85bb2fc551e56758606f764e57516b7f9a3
[06/12] xfs: hide b_flags manipulation from code outside of xfs_buf.c
        commit: 9f224de410d7efafc44ce1880aabd0101aa8688f
[07/12] xfs: use WRITE_ONCE to update b_flags
        commit: b15f6520ab6481b89688d4b6362d1fa5d9f9df6b
[08/12] xfs: don't reverify buffers in xfs_buf_readahead_map
        commit: 3d102727432b5c5cff9afa80a430ca8f34b59666
[09/12] xfs: use goto based error unwinding in xfs_buf_read_map
        commit: 819f1cc98aaf09733b30700608a02256f47d7908
[10/12] xfs: merge xfs_buf_reverify into xfs_buf_read_map
        commit: 21cc7775ee5ca2d5cd4be0de0d55fd28b14fd4e1
[11/12] xfs: move buffer locking out of xfs_find_get_buf
        commit: 2aedf844be1d578c4c2746177aaaf096a053d650
[12/12] xfs: add lockless xfs_buf_readahead_map fast path
        commit: 00f40876f417463ef759dc3b0c4cfe15da48b092

Best regards,
-- 
Carlos Maiolino <cem@kernel.org>


      parent reply	other threads:[~2026-08-10 11:55 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15 14:50 misc buffer cache improvements Christoph Hellwig
2026-07-15 14:50 ` [PATCH 01/12] xfs: don't get a pag reference in xfs_buf_get_map Christoph Hellwig
2026-07-24 16:32   ` Darrick J. Wong
2026-07-15 14:50 ` [PATCH 02/12] xfs: consolidate buffer locking " Christoph Hellwig
2026-07-16 13:12   ` Brian Foster
2026-07-17  8:59     ` Christoph Hellwig
2026-07-17 14:13       ` Brian Foster
2026-07-20  7:59         ` Christoph Hellwig
2026-07-24 16:42           ` Darrick J. Wong
2026-07-28  4:38             ` Christoph Hellwig
2026-07-15 14:50 ` [PATCH 03/12] xfs: split out a lower-level xfs_buf_get_map helper from xfs_find_get_buf Christoph Hellwig
2026-07-24 16:44   ` Darrick J. Wong
2026-07-28  4:39     ` Christoph Hellwig
2026-07-15 14:50 ` [PATCH 04/12] xfs: remove spurious XBF_DONE clearing on readahead validation failure Christoph Hellwig
2026-07-24 16:45   ` Darrick J. Wong
2026-07-15 14:50 ` [PATCH 05/12] xfs: remove _XBF_LOGRECOVERY Christoph Hellwig
2026-07-24 16:49   ` Darrick J. Wong
2026-07-28  4:39     ` Christoph Hellwig
2026-07-15 14:50 ` [PATCH 06/12] xfs: hide b_flags manipulation from code outside of xfs_buf.c Christoph Hellwig
2026-07-24 16:49   ` Darrick J. Wong
2026-07-15 14:51 ` [PATCH 07/12] xfs: use WRITE_ONCE to update b_flags Christoph Hellwig
2026-07-24 16:53   ` Darrick J. Wong
2026-07-28  4:40     ` Christoph Hellwig
2026-07-15 14:51 ` [PATCH 08/12] xfs: don't reverify buffers in xfs_buf_readahead_map Christoph Hellwig
2026-07-24 16:56   ` Darrick J. Wong
2026-07-15 14:51 ` [PATCH 09/12] xfs: use goto based error unwinding in xfs_buf_read_map Christoph Hellwig
2026-07-24 16:57   ` Darrick J. Wong
2026-07-15 14:51 ` [PATCH 10/12] xfs: merge xfs_buf_reverify into xfs_buf_read_map Christoph Hellwig
2026-07-17 14:13   ` Brian Foster
2026-07-24 16:58   ` Darrick J. Wong
2026-07-15 14:51 ` [PATCH 11/12] xfs: move buffer locking out of xfs_find_get_buf Christoph Hellwig
2026-07-24 16:59   ` Darrick J. Wong
2026-07-15 14:51 ` [PATCH 12/12] xfs: add lockless xfs_buf_readahead_map fast path Christoph Hellwig
2026-07-24 17:03   ` Darrick J. Wong
2026-07-28  4:41     ` Christoph Hellwig
2026-08-10 11:55 ` Carlos Maiolino [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=178636293365.58486.12109129017004452043.b4-ty@kernel.org \
    --to=cem@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox