Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Price <gourry@gourry.net>
To: SJ Park <sj@kernel.org>
Cc: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>,
	linux-mm@kvack.org, damon@lists.linux.dev,
	linux-kernel@vger.kernel.org, kernel-team@meta.com,
	akpm@linux-foundation.org, david@kernel.org, ziy@nvidia.com,
	baolin.wang@linux.alibaba.com, liam@infradead.org,
	npache@redhat.com, ryan.roberts@arm.com, dev.jain@arm.com,
	baohua@kernel.org, lance.yang@linux.dev, usama.arif@linux.dev,
	vbabka@kernel.org, jannh@google.com, matthew.brost@intel.com,
	joshua.hahnjy@gmail.com, rakie.kim@sk.com, byungchul@sk.com,
	ying.huang@linux.alibaba.com, apopple@nvidia.com
Subject: Re: [PATCH 1/4] mm/damon: defensively skip zone device folios in damon_get_folio()
Date: Wed, 12 Aug 2026 22:26:08 -0400	[thread overview]
Message-ID: <an0rQM7ZwWnB0nVD@fedora> (raw)
In-Reply-To: <20260807000938.79851-1-sj@kernel.org>

On Thu, Aug 06, 2026 at 05:09:37PM -0700, SJ Park wrote:
> On Thu, 6 Aug 2026 12:05:00 -0500 Gregory Price <gourry@gourry.net> wrote:
> 
> > On Thu, Aug 06, 2026 at 02:37:59PM +0100, Lorenzo Stoakes (ARM) wrote:
> > > On Tue, Jul 28, 2026 at 03:47:11PM -0400, Gregory Price wrote:
> > > > All DAMON physical- and virtual-address operations obtain their folios
> > > > through damon_get_folio(). That helper already excludes ZONE_DEVICE
> > > > memory implicitly via pfn_to_online_page() and folio_test_lru(), but
> > > > this is inconsistent with other callers in mm/ which test explicitly.
> > > >
> > > > Add an explicit folio_is_zone_device() rejection in damon_get_folio()
> > > > so the guarantee lives in one place and covers every caller uniformly,
> > > > consistent with other mm walkers that reject zone device folios.
> > > >
> > > > Signed-off-by: Gregory Price (Meta) <gourry@gourry.net>
> > > 
> > > Thanks, nice to make it explicit!
> > > 
> > > Acked-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
> > >
> > 
> > SJ Asked me to drop it,
> 
> I didn't asked you to drop this.  I asked your thought about revisioning this
> for my concern.  And you replied [1] you can drop this.
>

Sorry I didn't mean to imply you pushed for one side or another, just
that the feedback you gave about not wanting dead code is reason enough
to drop it.

I will probably just go ahead and drop it unless Lorenzo thinks the
patch is worth keeping.  In my next private node iteration, it ends up
back in anyway - so we get a two for one without the intermediate patch.

~Gregory


  reply	other threads:[~2026-08-13  2:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28 19:47 [PATCH 0/4] mm: reject zone device folios in more folio walkers Gregory Price
2026-07-28 19:47 ` [PATCH 1/4] mm/damon: defensively skip zone device folios in damon_get_folio() Gregory Price
2026-07-29  0:50   ` SJ Park
2026-07-29  2:01     ` Gregory Price
2026-07-29 14:22       ` SJ Park
2026-07-29 15:14         ` Gregory Price
2026-08-06 13:37   ` Lorenzo Stoakes (ARM)
2026-08-06 17:05     ` Gregory Price
2026-08-07  0:09       ` SJ Park
2026-08-13  2:26         ` Gregory Price [this message]
2026-07-28 19:47 ` [PATCH 2/4] mm/huge_memory: skip zone device folios in madvise_free_huge_pmd() Gregory Price
2026-08-06 13:20   ` David Hildenbrand (Arm)
2026-08-06 13:59   ` Lorenzo Stoakes (ARM)
2026-08-06 17:03     ` Gregory Price
2026-07-28 19:47 ` [PATCH 3/4] mm/madvise: skip zone device folios in cold/pageout PMD range Gregory Price
2026-08-06 13:23   ` David Hildenbrand (Arm)
2026-08-06 17:07     ` Gregory Price
2026-08-06 14:04   ` Lorenzo Stoakes (ARM)
2026-07-28 19:47 ` [PATCH 4/4] mm/mempolicy: skip zone device folios when queueing folios Gregory Price
2026-08-06 13:25   ` David Hildenbrand (Arm)
2026-08-06 13:36     ` Lorenzo Stoakes (ARM)
2026-08-06 14:11       ` David Hildenbrand (Arm)
2026-08-06 14:16         ` Lorenzo Stoakes (ARM)
2026-08-06 17:09           ` Gregory Price

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=an0rQM7ZwWnB0nVD@fedora \
    --to=gourry@gourry.net \
    --cc=akpm@linux-foundation.org \
    --cc=apopple@nvidia.com \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=byungchul@sk.com \
    --cc=damon@lists.linux.dev \
    --cc=david@kernel.org \
    --cc=dev.jain@arm.com \
    --cc=jannh@google.com \
    --cc=joshua.hahnjy@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=lance.yang@linux.dev \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=matthew.brost@intel.com \
    --cc=npache@redhat.com \
    --cc=rakie.kim@sk.com \
    --cc=ryan.roberts@arm.com \
    --cc=sj@kernel.org \
    --cc=usama.arif@linux.dev \
    --cc=vbabka@kernel.org \
    --cc=ying.huang@linux.alibaba.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