From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Chi Zhiling <chizhiling@163.com>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Cc: Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>, Zi Yan <ziy@nvidia.com>,
"Liam R. Howlett" <liam@infradead.org>,
Nico Pache <npache@redhat.com>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>, Lance Yang <lance.yang@linux.dev>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Jan Kara <jack@suse.cz>, Chi Zhiling <chizhiling@kylinos.cn>
Subject: Re: [RFC PATCH 3/4] mm/shmem: optimize file read with folio batching
Date: Tue, 19 May 2026 11:06:33 +0800 [thread overview]
Message-ID: <7db5253f-7cb7-45a7-91b6-8869ab9beb34@linux.alibaba.com> (raw)
In-Reply-To: <402906ba-4080-45a6-88c0-4cb8f88e2fa6@163.com>
On 5/19/26 10:15 AM, Chi Zhiling wrote:
> On 5/18/26 14:57, Baolin Wang wrote:
>>
>>
>> On 5/15/26 5:47 PM, Chi Zhiling wrote:
>>> From: Chi Zhiling <chizhiling@kylinos.cn>
>>>
>>> Optimize shmem file read by implementing folio batching in the read
>>> iteration path. Only uptodate folios are added to the batch, ensuring
>>> all folios in the batch are valid and ready for use without additional
>>> checking.
>>>
>>> Signed-off-by: Chi Zhiling <chizhiling@kylinos.cn>
>>> ---
>>> mm/shmem.c | 102 ++++++++++++++++++++++++++++++++++++++++++++++++-----
>>> 1 file changed, 93 insertions(+), 9 deletions(-)
>>>
>>> diff --git a/mm/shmem.c b/mm/shmem.c
>>> index 767610f78d0d..4bc4e463ca97 100644
>>> --- a/mm/shmem.c
>>> +++ b/mm/shmem.c
>>> @@ -3348,16 +3348,100 @@ shmem_write_end(const struct kiocb *iocb,
>>> struct address_space *mapping,
>>> return copied;
>>> }
>>> +static pgoff_t shmem_get_read_batch(struct address_space *mapping,
>>> + pgoff_t index, pgoff_t max, struct folio_batch *fbatch)
>>> +{
>>> + XA_STATE(xas, &mapping->i_pages, index);
>>> + struct folio *folio;
>>> + pgoff_t end = max;
>>> +
>>> + rcu_read_lock();
>>> + xas_for_each(&xas, folio, max) {
>>> + if (xas_retry(&xas, folio))
>>> + continue;
>>> + if (xa_is_value(folio)) {
>>> + end = xas.xa_index;
>>> + break;
>>> + }
>>> + if (!folio_try_get(folio))
>>> + goto retry;
>>> +
>>> + if (unlikely(folio != xas_reload(&xas)))
>>> + goto put_folio;
>>> +
>>> + end = folio_next_index(folio);
>>> +
>>> + if (!folio_test_uptodate(folio)) {
>>> + xas_advance(&xas, end - 1);
>>> + folio_put(folio);
>>> + continue;
>>> + }
>>> + if (!folio_batch_add(fbatch, folio))
>>> + break;
>>> + xas_advance(&xas, end - 1);
>>> + continue;
>>> +put_folio:
>>> + folio_put(folio);
>>> +retry:
>>> + xas_reset(&xas);
>>> + }
>>> + rcu_read_unlock();
>>> +
>>> + return end;
>>> +}
>>
>> I haven't looked at this patch in detail yet, but I feel this part
>> should belong in mm/filemap.c, or perhaps mm/filemap.c already has a
>> similar function implemented? Let's wait for Matthew's comments on this.
>
> You are right. The existing filemap_get_folios_contig can handle this
> with clearer code, nice!
Good.
next prev parent reply other threads:[~2026-05-19 3:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 9:46 [RFC PATCH 0/4] mm/shmem: optimize read performance " Chi Zhiling
2026-05-15 9:46 ` [RFC PATCH 1/4] mm/shmem: add SGP_GET to get unlocked folio Chi Zhiling
2026-05-15 9:47 ` [RFC PATCH 2/4] mm/shmem: use SGP_GET in read operations Chi Zhiling
2026-05-18 6:39 ` Baolin Wang
2026-05-18 7:42 ` Chi Zhiling
2026-05-19 3:06 ` Baolin Wang
2026-05-19 6:24 ` Chi Zhiling
2026-05-15 9:47 ` [RFC PATCH 3/4] mm/shmem: optimize file read with folio batching Chi Zhiling
2026-05-18 6:57 ` Baolin Wang
2026-05-18 8:05 ` Chi Zhiling
2026-05-19 2:15 ` Chi Zhiling
2026-05-19 3:06 ` Baolin Wang [this message]
2026-05-15 9:47 ` [RFC PATCH 4/4] mm/shmem: make SGP_NOALLOC succeed on hole like SGP_READ Chi Zhiling
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=7db5253f-7cb7-45a7-91b6-8869ab9beb34@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=chizhiling@163.com \
--cc=chizhiling@kylinos.cn \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=willy@infradead.org \
--cc=ziy@nvidia.com \
/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
all inboxes | Powered by JetHome®