From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Carlos Maiolino <cem@kernel.org>,
Dave Chinner <dchinner@redhat.com>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 04/12] xfs: remove xfs_buf_is_vmapped
Date: Wed, 26 Feb 2025 09:02:35 -0800 [thread overview]
Message-ID: <20250226170235.GO6242@frogsfrogsfrogs> (raw)
In-Reply-To: <20250226155245.513494-5-hch@lst.de>
On Wed, Feb 26, 2025 at 07:51:32AM -0800, Christoph Hellwig wrote:
> No need to look at the page count if we can simply call is_vmalloc_addr
> on bp->b_addr. This prepares for eventualy removing the b_page_count
> field.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Yeah, that's more direct.
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> fs/xfs/xfs_buf.c | 20 +++-----------------
> 1 file changed, 3 insertions(+), 17 deletions(-)
>
> diff --git a/fs/xfs/xfs_buf.c b/fs/xfs/xfs_buf.c
> index ee678e13d9bd..af1389ebdd69 100644
> --- a/fs/xfs/xfs_buf.c
> +++ b/fs/xfs/xfs_buf.c
> @@ -60,20 +60,6 @@ static inline bool xfs_buf_is_uncached(struct xfs_buf *bp)
> return bp->b_rhash_key == XFS_BUF_DADDR_NULL;
> }
>
> -static inline int
> -xfs_buf_is_vmapped(
> - struct xfs_buf *bp)
> -{
> - /*
> - * Return true if the buffer is vmapped.
> - *
> - * b_addr is null if the buffer is not mapped, but the code is clever
> - * enough to know it doesn't have to map a single page, so the check has
> - * to be both for b_addr and bp->b_page_count > 1.
> - */
> - return bp->b_addr && bp->b_page_count > 1;
> -}
> -
> static inline int
> xfs_buf_vmap_len(
> struct xfs_buf *bp)
> @@ -270,7 +256,7 @@ xfs_buf_free_pages(
>
> ASSERT(bp->b_flags & _XBF_PAGES);
>
> - if (xfs_buf_is_vmapped(bp))
> + if (is_vmalloc_addr(bp->b_addr))
> vm_unmap_ram(bp->b_addr, bp->b_page_count);
>
> for (i = 0; i < bp->b_page_count; i++) {
> @@ -1361,7 +1347,7 @@ xfs_buf_ioend(
> trace_xfs_buf_iodone(bp, _RET_IP_);
>
> if (bp->b_flags & XBF_READ) {
> - if (!bp->b_error && xfs_buf_is_vmapped(bp))
> + if (!bp->b_error && bp->b_addr && is_vmalloc_addr(bp->b_addr))
> invalidate_kernel_vmap_range(bp->b_addr,
> xfs_buf_vmap_len(bp));
> if (!bp->b_error && bp->b_ops)
> @@ -1533,7 +1519,7 @@ xfs_buf_submit_bio(
> __bio_add_page(bio, bp->b_pages[p], PAGE_SIZE, 0);
> bio->bi_iter.bi_size = size; /* limit to the actual size used */
>
> - if (xfs_buf_is_vmapped(bp))
> + if (bp->b_addr && is_vmalloc_addr(bp->b_addr))
> flush_kernel_vmap_range(bp->b_addr,
> xfs_buf_vmap_len(bp));
> }
> --
> 2.45.2
>
>
next prev parent reply other threads:[~2025-02-26 17:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 15:51 use folios and vmalloc for buffer cache backing memory Christoph Hellwig
2025-02-26 15:51 ` [PATCH 01/12] xfs: unmapped buffer item size straddling mismatch Christoph Hellwig
2025-02-26 15:51 ` [PATCH 02/12] xfs: add a fast path to xfs_buf_zero when b_addr is set Christoph Hellwig
2025-02-26 17:00 ` Darrick J. Wong
2025-02-26 15:51 ` [PATCH 03/12] xfs: remove xfs_buf.b_offset Christoph Hellwig
2025-02-26 17:00 ` Darrick J. Wong
2025-02-26 15:51 ` [PATCH 04/12] xfs: remove xfs_buf_is_vmapped Christoph Hellwig
2025-02-26 17:02 ` Darrick J. Wong [this message]
2025-02-26 15:51 ` [PATCH 05/12] xfs: refactor backing memory allocations for buffers Christoph Hellwig
2025-02-26 17:08 ` Darrick J. Wong
2025-02-26 15:51 ` [PATCH 06/12] xfs: remove the kmalloc to page allocator fallback Christoph Hellwig
2025-02-26 17:22 ` Darrick J. Wong
2025-03-04 14:05 ` Christoph Hellwig
2025-02-26 15:51 ` [PATCH 07/12] xfs: convert buffer cache to use high order folios Christoph Hellwig
2025-02-26 17:33 ` Darrick J. Wong
2025-03-04 14:06 ` Christoph Hellwig
2025-02-26 15:51 ` [PATCH 08/12] xfs: kill XBF_UNMAPPED Christoph Hellwig
2025-02-26 15:51 ` [PATCH 09/12] xfs: buffer items don't straddle pages anymore Christoph Hellwig
2025-02-26 15:51 ` [PATCH 10/12] xfs: use vmalloc instead of vm_map_area for buffer backing memory Christoph Hellwig
2025-02-26 18:02 ` Darrick J. Wong
2025-03-04 14:10 ` Christoph Hellwig
2025-02-26 15:51 ` [PATCH 11/12] xfs: cleanup mapping tmpfs folios into the buffer cache Christoph Hellwig
2025-02-26 17:39 ` Darrick J. Wong
2025-03-04 14:11 ` Christoph Hellwig
2025-02-26 15:51 ` [PATCH 12/12] xfs: trace what memory backs a buffer Christoph Hellwig
2025-02-26 16:45 ` Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2025-03-05 14:05 use folios and vmalloc for buffer cache backing memory v2 Christoph Hellwig
2025-03-05 14:05 ` [PATCH 04/12] xfs: remove xfs_buf_is_vmapped Christoph Hellwig
2025-03-10 13:19 use folios and vmalloc for buffer cache backing memory v3 Christoph Hellwig
2025-03-10 13:19 ` [PATCH 04/12] xfs: remove xfs_buf_is_vmapped 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=20250226170235.GO6242@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=dchinner@redhat.com \
--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.