From: Mike Rapoport <rppt@kernel.org>
To: Gladyshev Ilya <ilya.gladyshev@linux.dev>
Cc: Linus Torvalds <torvalds@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
ivgorbunov@me.com, Liam.Howlett@oracle.com, apopple@nvidia.com,
artem.kuzin@huawei.com, baolin.wang@linux.alibaba.com,
foxido@foxido.dev, harry.yoo@oracle.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
lorenzo.stoakes@oracle.com, mhocko@suse.com,
muchun.song@linux.dev, surenb@google.com, vbabka@suse.cz,
yuzhao@google.com, ziy@nvidia.com, pfalcato@suse.de,
kirill@shutemov.name
Subject: Re: [PATCH v5 0/2] mm: improve folio refcount scalability
Date: Sat, 27 Jun 2026 11:10:27 +0300 [thread overview]
Message-ID: <aj-Fc9hCSj51RYbP@kernel.org> (raw)
In-Reply-To: <bb1cb750157733f897df2e261cad3d5c42acc172@linux.dev>
On Fri, Jun 26, 2026 at 06:44:58PM +0000, Gladyshev Ilya wrote:
>
> This patch optimizes small file read performance and overall folio refcount
> scalability by refactoring page_ref_add_unless [core of folio_try_get].
> This is alternative approach to previous attempts to fix small read
> performance by avoiding refcount bumps [1][2].
Looks like memory-failure selftest is not happy:
https://github.com/linux-mm/linux-mm/actions/runs/28259343162/job/83730467505
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2026-06-27 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 18:44 [PATCH v5 0/2] mm: improve folio refcount scalability Gladyshev Ilya
2026-06-26 18:46 ` [PATCH v5 1/2] mm: drop page refcount zero state semantics Gladyshev Ilya
2026-06-26 18:46 ` [PATCH v5 2/2] mm: implement page refcount locking via dedicated bit Gladyshev Ilya
2026-06-27 1:15 ` [PATCH v5 0/2] mm: improve folio refcount scalability Andrew Morton
2026-06-27 8:10 ` Mike Rapoport [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=aj-Fc9hCSj51RYbP@kernel.org \
--to=rppt@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=artem.kuzin@huawei.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=foxido@foxido.dev \
--cc=harry.yoo@oracle.com \
--cc=ilya.gladyshev@linux.dev \
--cc=ivgorbunov@me.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=pfalcato@suse.de \
--cc=surenb@google.com \
--cc=torvalds@linuxfoundation.org \
--cc=vbabka@suse.cz \
--cc=yuzhao@google.com \
--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