From: Carlos Maiolino <cem@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Dave Chinner <dchinner@redhat.com>,
linux-xfs@vger.kernel.org
Subject: Re: use folios and vmalloc for buffer cache backing memory v3
Date: Fri, 14 Mar 2025 14:27:15 +0100 [thread overview]
Message-ID: <174195883507.416085.1719150270205198201.b4-ty@kernel.org> (raw)
In-Reply-To: <20250310131917.552600-1-hch@lst.de>
On Mon, 10 Mar 2025 14:19:03 +0100, Christoph Hellwig wrote:
> this is another spin on converting the XFS buffer cache to use folios and
> generally simplify the memory allocation in it. It is based on Dave's
> last folio series (which itself had pulled in bits from my earlier
> vmalloc series).
>
> It converts the backing memory allocation for all large buffers that are
> power of two sized to large folios, converts > PAGE_SIZE but not power of
> two allocations to vmalloc instead of vm_map_ram and generally cleans up
> a lot of code around the memory allocation and reduces the size of the
> xfs_buf structure by removing the embedded pages array and pages pointer.
>
> [...]
Applied to for-next, thanks!
[01/12] xfs: unmapped buffer item size straddling mismatch
commit: 69659e46b7588d2fd5e4644dec9e61127bbfd5f3
[02/12] xfs: add a fast path to xfs_buf_zero when b_addr is set
commit: f2a3717a74c2cf01e29ea3aba355e171eb0d5f5f
[03/12] xfs: remove xfs_buf.b_offset
commit: 51e10993153adc14e8caf2a13d6defc8403dfb4c
[04/12] xfs: remove xfs_buf_is_vmapped
commit: 48a325a4eec3251c2ead7ad7dad304bbdc1460a0
[05/12] xfs: refactor backing memory allocations for buffers
commit: 50a524e0ef9be0e862207fc822ab4b7dcb0c4310
[06/12] xfs: remove the kmalloc to page allocator fallback
commit: 4ef39828318220f11050984fb8dbc372c9c03960
[07/12] xfs: convert buffer cache to use high order folios
commit: 94c78cfa3bd1858eec3c462aedeb7f297d38d768
[08/12] xfs: kill XBF_UNMAPPED
commit: a2f790b28512c22f7cf4f420a99e1b008e7098fe
[09/12] xfs: buffer items don't straddle pages anymore
commit: fd87851680edcb931b2ec4caf23b4abbea126fc3
[10/12] xfs: use vmalloc instead of vm_map_area for buffer backing memory
commit: e2874632a6213b4687e53cd7d837c642c805c903
[11/12] xfs: cleanup mapping tmpfs folios into the buffer cache
commit: e614a00117bc2d46219c66a287ddde0f0a04517c
[12/12] xfs: trace what memory backs a buffer
commit: 89ce287c83c91f5d222809b82e597426587a862d
Best regards,
--
Carlos Maiolino <cem@kernel.org>
prev parent reply other threads:[~2025-03-14 13:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 13:19 use folios and vmalloc for buffer cache backing memory v3 Christoph Hellwig
2025-03-10 13:19 ` [PATCH 01/12] xfs: unmapped buffer item size straddling mismatch Christoph Hellwig
2025-03-10 13:19 ` [PATCH 02/12] xfs: add a fast path to xfs_buf_zero when b_addr is set Christoph Hellwig
2025-03-10 13:19 ` [PATCH 03/12] xfs: remove xfs_buf.b_offset Christoph Hellwig
2025-03-10 13:19 ` [PATCH 04/12] xfs: remove xfs_buf_is_vmapped Christoph Hellwig
2025-03-10 13:19 ` [PATCH 05/12] xfs: refactor backing memory allocations for buffers Christoph Hellwig
2025-03-10 13:19 ` [PATCH 06/12] xfs: remove the kmalloc to page allocator fallback Christoph Hellwig
2025-03-10 13:19 ` [PATCH 07/12] xfs: convert buffer cache to use high order folios Christoph Hellwig
2025-03-10 13:19 ` [PATCH 08/12] xfs: kill XBF_UNMAPPED Christoph Hellwig
2025-03-10 13:19 ` [PATCH 09/12] xfs: buffer items don't straddle pages anymore Christoph Hellwig
2025-03-10 13:19 ` [PATCH 10/12] xfs: use vmalloc instead of vm_map_area for buffer backing memory Christoph Hellwig
2025-03-10 13:19 ` [PATCH 11/12] xfs: cleanup mapping tmpfs folios into the buffer cache Christoph Hellwig
2025-03-10 13:19 ` [PATCH 12/12] xfs: trace what memory backs a buffer Christoph Hellwig
2025-03-14 13:27 ` 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=174195883507.416085.1719150270205198201.b4-ty@kernel.org \
--to=cem@kernel.org \
--cc=dchinner@redhat.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.