linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/8] filemap: Remove readahead_page()
Date: Fri, 4 Apr 2025 22:52:42 +0200	[thread overview]
Message-ID: <17a7dee4-ed2f-4b09-b020-1cff3be69ad7@redhat.com> (raw)
In-Reply-To: <20250402210612.2444135-2-willy@infradead.org>

On 02.04.25 23:06, Matthew Wilcox (Oracle) wrote:
> All filesystems have now been converted to call readahead_folio()
> so we can delete this wrapper.
> 
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> ---
>   include/linux/pagemap.h | 22 +++-------------------
>   1 file changed, 3 insertions(+), 19 deletions(-)
> 
> diff --git a/include/linux/pagemap.h b/include/linux/pagemap.h
> index 26baa78f1ca7..cd4bd0f8e5f6 100644
> --- a/include/linux/pagemap.h
> +++ b/include/linux/pagemap.h
> @@ -1308,9 +1308,9 @@ static inline bool filemap_range_needs_writeback(struct address_space *mapping,
>    * struct readahead_control - Describes a readahead request.
>    *
>    * A readahead request is for consecutive pages.  Filesystems which
> - * implement the ->readahead method should call readahead_page() or
> - * readahead_page_batch() in a loop and attempt to start I/O against
> - * each page in the request.
> + * implement the ->readahead method should call readahead_folio() or
> + * __readahead_batch() in a loop and attempt to start reads into each
> + * folio in the request.
>    *
>    * Most of the fields in this struct are private and should be accessed
>    * by the functions below.
> @@ -1415,22 +1415,6 @@ static inline struct folio *__readahead_folio(struct readahead_control *ractl)
>   	return folio;
>   }
>   
> -/**
> - * readahead_page - Get the next page to read.
> - * @ractl: The current readahead request.
> - *
> - * Context: The page is locked and has an elevated refcount.  The caller
> - * should decreases the refcount once the page has been submitted for I/O
> - * and unlock the page once all I/O to that page has completed.
> - * Return: A pointer to the next page, or %NULL if we are done.
> - */
> -static inline struct page *readahead_page(struct readahead_control *ractl)
> -{
> -	struct folio *folio = __readahead_folio(ractl);
> -
> -	return &folio->page;
> -}
> -
>   /**
>    * readahead_folio - Get the next folio to read.
>    * @ractl: The current readahead request.

Reviewed-by: David Hildenbrand <david@redhat.com>

-- 
Cheers,

David / dhildenb


  reply	other threads:[~2025-04-04 20:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-02 21:06 [PATCH 0/8] Misc folio patches for 6.16 Matthew Wilcox (Oracle)
2025-04-02 21:06 ` [PATCH 1/8] filemap: Remove readahead_page() Matthew Wilcox (Oracle)
2025-04-04 20:52   ` David Hildenbrand [this message]
2025-04-02 21:06 ` [PATCH 2/8] mm: Remove offset_in_thp() Matthew Wilcox (Oracle)
2025-04-04 20:52   ` David Hildenbrand
2025-04-02 21:06 ` [PATCH 3/8] iov_iter: Convert iter_xarray_populate_pages() to use folios Matthew Wilcox (Oracle)
2025-04-04 20:53   ` David Hildenbrand
2025-04-02 21:06 ` [PATCH 4/8] iov_iter: Convert iov_iter_extract_xarray_pages() " Matthew Wilcox (Oracle)
2025-04-04 20:56   ` David Hildenbrand
2025-04-02 21:06 ` [PATCH 5/8] filemap: Remove find_subpage() Matthew Wilcox (Oracle)
2025-04-04 20:57   ` David Hildenbrand
2025-04-02 21:06 ` [PATCH 6/8] filemap: Convert __readahead_batch() to use a folio Matthew Wilcox (Oracle)
2025-04-04 20:59   ` David Hildenbrand
2025-04-02 21:06 ` [PATCH 7/8] filemap: Remove readahead_page_batch() Matthew Wilcox (Oracle)
2025-04-04 21:00   ` David Hildenbrand
2025-04-02 21:06 ` [PATCH 8/8] mm: Delete thp_nr_pages() Matthew Wilcox (Oracle)
2025-04-04 21:00   ` David Hildenbrand

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=17a7dee4-ed2f-4b09-b020-1cff3be69ad7@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).