Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Byungchul Park <byungchul@sk.com>
Cc: Dragos Tatulea <dtatulea@nvidia.com>,
	linux-mm@kvack.org, akpm@linux-foundation.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel_team@skhynix.com, harry.yoo@oracle.com, ast@kernel.org,
	daniel@iogearbox.net, davem@davemloft.net, kuba@kernel.org,
	hawk@kernel.org, john.fastabend@gmail.com, sdf@fomichev.me,
	saeedm@nvidia.com, leon@kernel.org, tariqt@nvidia.com,
	mbloch@nvidia.com, andrew+netdev@lunn.ch, edumazet@google.com,
	pabeni@redhat.com, lorenzo.stoakes@oracle.com,
	Liam.Howlett@oracle.com, vbabka@suse.cz, rppt@kernel.org,
	surenb@google.com, mhocko@suse.com, horms@kernel.org,
	jackmanb@google.com, hannes@cmpxchg.org, ziy@nvidia.com,
	ilias.apalodimas@linaro.org, willy@infradead.org,
	brauner@kernel.org, kas@kernel.org, yuzhao@google.com,
	usamaarif642@gmail.com, baolin.wang@linux.alibaba.com,
	almasrymina@google.com, toke@redhat.com, asml.silence@gmail.com,
	bpf@vger.kernel.org, linux-rdma@vger.kernel.org,
	sfr@canb.auug.org.au, dw@davidwei.uk, ap420073@gmail.com
Subject: Re: [PATCH v4] mm: introduce a new page type for page pool in page type
Date: Mon, 18 May 2026 11:33:59 +0200	[thread overview]
Message-ID: <65d11b12-5696-4403-8062-3ae65ca9113e@kernel.org> (raw)
In-Reply-To: <20260513132636.GA75142@system.software.com>

On 5/13/26 15:26, Byungchul Park wrote:
> On Wed, May 13, 2026 at 03:02:43PM +0200, David Hildenbrand (Arm) wrote:
>> On 5/13/26 14:39, Byungchul Park wrote:
>>>  On 5/13/26 14:18, Byungchul Park wrote:
>>>
>>> This is not final patch, but for sharing the rough idea *with code* -
>>> maybe there are more points in code that should be adjusted by the
>>> change.  I just typed the draft patch quick just for sharing idea.
>>>
>>> If we should allow pp type pages to be used in mapping as well, then
>>> we should allow a page to keep both its type and mapcount at the same
>>> time.  Am I missing something?
>>
>> We don't want code to accidentally overflow mapcounts into these bits and have
>> them wrongly be detected as page types.
>>
>> This is just very fragile.
> 
> Okay.  Thanks for the explanation.  Plus, the adjustment I mentioned
> might not be as simple as I thought it'd be.
> 
> So sorry about the noise.  I'm a zombie now.  I'll think about it after
> some rest.

It's a shame we didn't get reports earlier that we do have some vm_insert_page()
users :(

-- 
Cheers,

David

  reply	other threads:[~2026-05-18  9:34 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24  5:13 [PATCH v4] mm: introduce a new page type for page pool in page type Byungchul Park
2026-02-25  7:19 ` Mike Rapoport
2026-02-26 18:49 ` Johannes Weiner
2026-03-16 22:29   ` Byungchul Park
2026-03-16 22:31     ` [PATCH v5] " Byungchul Park
2026-03-17  9:20       ` Jesper Dangaard Brouer
2026-03-17 10:03         ` Ilias Apalodimas
2026-03-17 11:06         ` Dragos Tatulea
2026-03-19 23:31           ` Jakub Kicinski
2026-03-18  2:02         ` Byungchul Park
2026-03-20 11:44           ` Jesper Dangaard Brouer
2026-03-23 12:16             ` Ilias Apalodimas
2026-03-19 23:31       ` Jakub Kicinski
2026-05-13  9:00 ` [PATCH v4] " Dragos Tatulea
2026-05-13  9:12   ` Vlastimil Babka (SUSE)
2026-05-13  9:26     ` Pedro Falcato
2026-05-13  9:36       ` David Hildenbrand (Arm)
2026-05-13 12:06         ` Dragos Tatulea
2026-05-13 12:11           ` David Hildenbrand (Arm)
2026-05-14  8:54           ` Byungchul Park
2026-05-14  9:24             ` Dragos Tatulea
2026-05-15  0:01               ` Byungchul Park
2026-05-13  9:34   ` David Hildenbrand (Arm)
2026-05-13 12:18   ` Byungchul Park
2026-05-13 12:29     ` David Hildenbrand (Arm)
2026-05-13 12:39       ` Byungchul Park
2026-05-13 13:02         ` David Hildenbrand (Arm)
2026-05-13 13:26           ` Byungchul Park
2026-05-18  9:33             ` David Hildenbrand (Arm) [this message]
2026-05-13  9:42 ` Lorenzo Stoakes

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=65d11b12-5696-4403-8062-3ae65ca9113e@kernel.org \
    --to=david@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=almasrymina@google.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=ap420073@gmail.com \
    --cc=asml.silence@gmail.com \
    --cc=ast@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=bpf@vger.kernel.org \
    --cc=brauner@kernel.org \
    --cc=byungchul@sk.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=dtatulea@nvidia.com \
    --cc=dw@davidwei.uk \
    --cc=edumazet@google.com \
    --cc=hannes@cmpxchg.org \
    --cc=harry.yoo@oracle.com \
    --cc=hawk@kernel.org \
    --cc=horms@kernel.org \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jackmanb@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=kas@kernel.org \
    --cc=kernel_team@skhynix.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mbloch@nvidia.com \
    --cc=mhocko@suse.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rppt@kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=sdf@fomichev.me \
    --cc=sfr@canb.auug.org.au \
    --cc=surenb@google.com \
    --cc=tariqt@nvidia.com \
    --cc=toke@redhat.com \
    --cc=usamaarif642@gmail.com \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.org \
    --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