From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: hch@lst.de, linux-xfs@vger.kernel.org, willy@infradead.org
Subject: Re: [PATCH 1/5] xfs: teach buftargs to maintain their own buffer hashtable
Date: Thu, 1 Feb 2024 22:26:35 -0800 [thread overview]
Message-ID: <ZbyLG3aktCcxp_iL@infradead.org> (raw)
In-Reply-To: <170681336975.1608400.15103821354987789245.stgit@frogsfrogsfrogs>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2024-02-02 6:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 19:39 [PATCHSET v29.2 6/8] xfs: support in-memory btrees Darrick J. Wong
2024-02-01 19:57 ` [PATCH 1/5] xfs: teach buftargs to maintain their own buffer hashtable Darrick J. Wong
2024-02-02 6:26 ` Christoph Hellwig [this message]
2024-02-01 19:57 ` [PATCH 2/5] xfs: support in-memory buffer cache targets Darrick J. Wong
2024-02-02 6:27 ` Christoph Hellwig
2024-02-01 19:58 ` [PATCH 3/5] xfs: add a xfs_btree_ptrs_equal helper Darrick J. Wong
2024-02-01 19:58 ` [PATCH 4/5] xfs: support in-memory btrees Darrick J. Wong
2024-02-02 6:27 ` Christoph Hellwig
2024-02-01 19:58 ` [PATCH 5/5] xfs: launder in-memory btree buffers before transaction commit Darrick J. Wong
2024-02-02 6:27 ` 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=ZbyLG3aktCcxp_iL@infradead.org \
--to=hch@infradead.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
--cc=willy@infradead.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