lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20250616224827.3009-1-sj@kernel.org>
Date: Mon, 16 Jun 2025 15:48:27 -0700
From: SeongJae Park <sj@...nel.org>
To: Joshua Hahn <joshua.hahnjy@...il.com>
Cc: SeongJae Park <sj@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	David Hildenbrand <david@...hat.com>,
	Honggyu Kim <honggyu.kim@...com>,
	Johannes Weiner <hannes@...xchg.org>,
	Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
	Michal Hocko <mhocko@...nel.org>,
	Qi Zheng <zhengqi.arch@...edance.com>,
	Shakeel Butt <shakeel.butt@...ux.dev>,
	damon@...ts.linux.dev,
	kernel-team@...a.com,
	linux-kernel@...r.kernel.org,
	linux-mm@...ck.org
Subject: Re: [PATCH 0/3] mm/damon: use alloc_migrate_target() for DAMOS_MIGRATE_{HOT,COLD}

Hi Joshua,

On Mon, 16 Jun 2025 14:31:58 -0700 Joshua Hahn <joshua.hahnjy@...il.com> wrote:

> On Mon, 16 Jun 2025 10:23:43 -0700 SeongJae Park <sj@...nel.org> wrote:
> 
> > DAMOS_MIGRATE_{HOT,COLD} implementation resembles that for demotion, and
> > hence the behavior is also similar to that.  But, since those are not
> > only for demotion but general migrations, it would be better to match
> > with that for move_pages() system call.  Make the implementation and the
> > behavior more similar to move_pages() by not setting migration fallback
> > nodes, and using alloc_migration_target() instead of
> > alloc_migrate_folio().
> > 
> > alloc_migrate_folio() was renamed from alloc_demote_folio() and been
> > non-static function, to let DAMOS_MIGRATE_{HOT,COLD} call it.  As
> > alloc_migration_target() is called instead, the renaming and de-static
> > changes are no more required but could only make future code readers be
> > confused.  Revert the changes, too.
> 
> Hi SJ,
> I hope you are doing well!

Thank you, you too! :)

> 
> These changes all look good to me. And I agree that changing the behavior
> to mimic migration as opposed to demotion might be helpful in making
> opportunities for others to use DAMOS as a means to perform other related
> works (like [1]), without having to use a "demotion" mechanism for simply
> moving pages around.
> 
> I do have one question: I'm curious what kinds of changes callers can expect.
> Would I be correct in understanding that this is mostly a semantic change
> (aside from no longer having a fallback nodemask)? Just want to make sure I
> have a correct understanding of your intent was.

You're correct.  This is not changing any DAMON interface, so DAMON API callers
and DAMON ABI users would not need to make any change from their side.

> 
> In the meantime, feel free to add the following to the series:
> Reviewed-by: Joshua Hahn <joshua.hahnjy@...il.com>

Thank you! :)

> 
> Have a great day!


You too!


Thanks,
SJ

[...]

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ