linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Byungchul Park <byungchul@sk.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	kernel_team@skhynix.com, akpm@linux-foundation.org,
	ying.huang@intel.com, namit@vmware.com, xhao@linux.alibaba.com,
	mgorman@techsingularity.net, hughd@google.com, david@redhat.com,
	peterz@infradead.org, luto@kernel.org, tglx@linutronix.de,
	mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com
Subject: Re: [v5 4/7] mm: Separate move/undo doing on folio list from migrate_pages_batch()
Date: Thu, 11 Jan 2024 15:42:55 +0000	[thread overview]
Message-ID: <ZaAMf5JX2D3N7Epi@casper.infradead.org> (raw)
In-Reply-To: <20240111060757.13563-5-byungchul@sk.com>

On Thu, Jan 11, 2024 at 03:07:54PM +0900, Byungchul Park wrote:
> +static void migrate_folios_move(struct list_head *src_folios,
> +		struct list_head *dst_folios,
> +		free_folio_t put_new_folio, unsigned long private,
> +		enum migrate_mode mode, int reason,
> +		struct list_head *ret_folios,
> +		struct migrate_pages_stats *stats,
> +		int *retry, int *thp_retry, int *nr_failed,
> +		int *nr_retry_pages)
> +{
> +	struct folio *folio, *folio2, *dst, *dst2;
> +	bool is_thp;
> +	int nr_pages;
> +	int rc;
> +
> +	dst = list_first_entry(dst_folios, struct folio, lru);
> +	dst2 = list_next_entry(dst, lru);
> +	list_for_each_entry_safe(folio, folio2, src_folios, lru) {
> +		is_thp = folio_test_large(folio) && folio_test_pmd_mappable(folio);

You don't need to call folio_test_large() first.  folio_order() includes
a call to test_large() so it can return 0.

> +		nr_pages = folio_nr_pages(folio);

... or since you're calculating this anyway,

		is_thp = nr_pages >= HPAGE_PMD_NR
perhaps



  reply	other threads:[~2024-01-11 15:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11  6:07 [v5 0/7] Reduce TLB flushes by 94% by improving folio migration Byungchul Park
2024-01-11  6:07 ` [v5 1/7] x86/tlb: Add APIs manipulating tlb batch's arch data Byungchul Park
2024-01-11  6:07 ` [v5 2/7] arm64: tlbflush: " Byungchul Park
2024-01-11  6:07 ` [v5 3/7] mm/rmap: Recognize read-only TLB entries during batched TLB flush Byungchul Park
2024-01-11  6:07 ` [v5 4/7] mm: Separate move/undo doing on folio list from migrate_pages_batch() Byungchul Park
2024-01-11 15:42   ` Matthew Wilcox [this message]
2024-01-15  2:08     ` Byungchul Park
2024-01-15  8:48       ` Byungchul Park
2024-01-11  6:07 ` [v5 5/7] mm: Add APIs to free a folio directly to the buddy bypassing pcp Byungchul Park
2024-01-11  6:07 ` [v5 6/7] mm: Defer TLB flush by keeping both src and dst folios at migration Byungchul Park
2024-01-11 18:44   ` kernel test robot
2024-01-11 19:58   ` kernel test robot
2024-01-11 22:12   ` kernel test robot
2024-01-11  6:07 ` [v5 7/7] mm: Pause migrc mechanism at high memory pressure Byungchul Park

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=ZaAMf5JX2D3N7Epi@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=byungchul@sk.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=david@redhat.com \
    --cc=hughd@google.com \
    --cc=kernel_team@skhynix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@kernel.org \
    --cc=mgorman@techsingularity.net \
    --cc=mingo@redhat.com \
    --cc=namit@vmware.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=xhao@linux.alibaba.com \
    --cc=ying.huang@intel.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