From: Gladyshev Ilya <gladyshev.ilya1@h-partners.com>
To: Kiryl Shutsemau <kirill@shutemov.name>
Cc: <guohanjun@huawei.com>, <wangkefeng.wang@huawei.com>,
<weiyongjun1@huawei.com>, <yusongping@huawei.com>,
<leijitang@huawei.com>, <artem.kuzin@huawei.com>,
<stepanov.anatoly@huawei.com>, <alexander.grubnikov@huawei.com>,
<gorbunov.ivan@h-partners.com>, <akpm@linux-foundation.org>,
<david@kernel.org>, <lorenzo.stoakes@oracle.com>,
<Liam.Howlett@oracle.com>, <vbabka@suse.cz>, <rppt@kernel.org>,
<surenb@google.com>, <mhocko@suse.com>, <ziy@nvidia.com>,
<harry.yoo@oracle.com>, <willy@infradead.org>,
<yuzhao@google.com>, <baolin.wang@linux.alibaba.com>,
<muchun.song@linux.dev>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/2] mm: improve folio refcount scalability
Date: Mon, 12 Jan 2026 17:32:10 +0300 [thread overview]
Message-ID: <d9fe0fb8-2c83-4eeb-8513-853522909253@h-partners.com> (raw)
In-Reply-To: <aWTfduyPXjhymyzW@thinkstation>
On 1/12/2026 2:49 PM, Kiryl Shutsemau wrote:
> On Mon, Jan 12, 2026 at 11:30:38AM +0300, Gladyshev Ilya wrote:
>> Gentle ping on this proposal
>
> I generally like the idea, but I would like to hear from folks who
> actually understand serialization.
>
> Also, do you have number for "a full CAS loop when the counter is
> approaching overflow" thing?
>
I am not sure that overflow is a real problem because you need a very
specific race condition over a long time to achieve it... But as a
safeguard, everything lower than 2^31 - #max concurrent accesses (~#num
cpu) should work, so let's say 2^30
next prev parent reply other threads:[~2026-01-12 14:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 12:46 [RFC PATCH 0/2] mm: improve folio refcount scalability Gladyshev Ilya
2025-12-19 12:46 ` [RFC PATCH 1/2] mm: make ref_unless functions unless_zero only Gladyshev Ilya
2026-02-06 13:16 ` David Hildenbrand (Arm)
2025-12-19 12:46 ` [RFC PATCH 2/2] mm: implement page refcount locking via dedicated bit Gladyshev Ilya
2025-12-19 14:50 ` Kiryl Shutsemau
2025-12-19 16:18 ` Gladyshev Ilya
2025-12-19 17:46 ` Kiryl Shutsemau
2025-12-19 19:08 ` Gladyshev Ilya
2025-12-22 13:33 ` Kiryl Shutsemau
2025-12-19 18:17 ` Gregory Price
2025-12-22 12:42 ` Gladyshev Ilya
2026-01-12 8:30 ` [RFC PATCH 0/2] mm: improve folio refcount scalability Gladyshev Ilya
2026-01-12 11:49 ` Kiryl Shutsemau
2026-01-12 14:32 ` Gladyshev Ilya [this message]
2026-01-12 16:17 ` Kiryl Shutsemau
2026-01-13 7:31 ` Gladyshev Ilya
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=d9fe0fb8-2c83-4eeb-8513-853522909253@h-partners.com \
--to=gladyshev.ilya1@h-partners.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.grubnikov@huawei.com \
--cc=artem.kuzin@huawei.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=gorbunov.ivan@h-partners.com \
--cc=guohanjun@huawei.com \
--cc=harry.yoo@oracle.com \
--cc=kirill@shutemov.name \
--cc=leijitang@huawei.com \
--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=rppt@kernel.org \
--cc=stepanov.anatoly@huawei.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=wangkefeng.wang@huawei.com \
--cc=weiyongjun1@huawei.com \
--cc=willy@infradead.org \
--cc=yusongping@huawei.com \
--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