All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Usama Arif <usamaarif642@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
	akpm@linux-foundation.org, damon@lists.linux.dev,
	linux-mm@kvack.org
Subject: Re: [v1 1/2] mm/damon: have damon_get_folio return folio even for tail pages
Date: Thu, 16 Jan 2025 10:49:32 -0800	[thread overview]
Message-ID: <20250116184932.23409-1-sj@kernel.org> (raw)
In-Reply-To: <20250116144436.3947318-1-usamaarif642@gmail.com>

On Thu, 16 Jan 2025 14:44:35 +0000 Usama Arif <usamaarif642@gmail.com> wrote:

> This effectively adds support for large folios in damon for paddr,
> as damon_pa_mkold/young won't get a null folio from this function
> and won't ignore it, hence access will be checked and reported.
> This also means that larger folios will be considered for
> different DAMOS actions like pageout, prioritization and migration.
> As these DAMOS actions will consider larger folios, iterate through
> the region at folio_size and not PAGE_SIZE intervals.
> This should not have an affect on vaddr, as damon_young_pmd_entry
> considers pmd entries.

This patch will improve both accuracy of monitoring results and efficiency of
DAMOS for paddr use cases on THP-enabled systems.  Thank you Usama!

> 
> Signed-off-by: Usama Arif <usamaarif642@gmail.com>

Reviewed-by: SeongJae Park <sj@kernel.org>


Thanks,
SJ

[...]

      parent reply	other threads:[~2025-01-16 18:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16 14:44 [v1 1/2] mm/damon: have damon_get_folio return folio even for tail pages Usama Arif
2025-01-16 14:44 ` [v1 2/2] mm/damon: introduce DAMOS filter type hugepage Usama Arif
2025-01-16 15:15   ` Usama Arif
2025-01-16 19:07     ` SeongJae Park
2025-01-16 19:05   ` SeongJae Park
2025-01-17 11:02     ` Usama Arif
2025-01-17 17:08       ` SeongJae Park
2025-01-18  8:09   ` kernel test robot
2025-01-18 10:34   ` kernel test robot
2025-01-16 18:49 ` SeongJae Park [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=20250116184932.23409-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=damon@lists.linux.dev \
    --cc=linux-mm@kvack.org \
    --cc=usamaarif642@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.