From: Rik van Riel <riel@surriel.com>
To: Gregory Price <gourry.memverge@gmail.com>, linux-mm@kvack.org
Cc: akpm@linux-foundation.org, willy@infradead.org, david@redhat.com,
vbabka@suse.cz, naoya.horiguchi@linux.dev,
linux-kernel@vger.kernel.org,
Gregory Price <gregory.price@memverge.com>
Subject: Re: [PATCH] kpageflags: respect folio head-page flag placement
Date: Wed, 25 Oct 2023 21:34:15 -0400 [thread overview]
Message-ID: <3ac68b3be0f62cfcd930ee84b87fbdc8244fe45e.camel@surriel.com> (raw)
In-Reply-To: <20231025201237.948993-1-gregory.price@memverge.com>
On Wed, 2023-10-25 at 16:12 -0400, Gregory Price wrote:
>
> +++ b/fs/proc/page.c
> @@ -188,20 +188,31 @@ u64 stable_page_flags(struct page *page)
> u |= 1 << KPF_SLAB;
>
> u |= kpf_copy_bit(k, KPF_ERROR, PG_error);
> - u |= kpf_copy_bit(k, KPF_DIRTY, PG_dirty);
> +
> + if (PageDirty(page))
> + u |= 1 << KPF_DIRTY;
> +
> u |= kpf_copy_bit(k, KPF_UPTODATE, PG_uptodate);
> u |= kpf_copy_bit(k, KPF_WRITEBACK, PG_writeback);
>
> - u |= kpf_copy_bit(k, KPF_LRU, PG_lru);
> - u |= kpf_copy_bit(k, KPF_REFERENCED, PG_referenced);
> - u |= kpf_copy_bit(k, KPF_ACTIVE, PG_active);
> + if (PageLRU(page))
> + u |= 1 << KPF_LRU;
> +
> + if (PageReferenced(page))
> + u |= 1 << KPF_REFERENCED;
> +
> + if (PageActive(page))
> + u |= 1 << KPF_ACTIVE;
> +
> u |= kpf_copy_bit(k, KPF_RECLAIM, PG_reclaim);
>
> if (PageSwapCache(page))
> u |= 1 << KPF_SWAPCACHE;
> u |= kpf_copy_bit(k, KPF_SWAPBACKED, PG_swapbacked);
>
Aren't PG_locked, PG_reclaim, and PG_swapbacked also maintained only on
the folio/head?
Would it make sense to convert those over as well?
--
All Rights Reversed.
next prev parent reply other threads:[~2023-10-26 1:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 20:12 [PATCH] kpageflags: respect folio head-page flag placement Gregory Price
2023-10-26 1:34 ` Rik van Riel [this message]
2023-10-26 19:12 ` Gregory Price
2023-10-26 20:00 ` Matthew Wilcox
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=3ac68b3be0f62cfcd930ee84b87fbdc8244fe45e.camel@surriel.com \
--to=riel@surriel.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gourry.memverge@gmail.com \
--cc=gregory.price@memverge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@linux.dev \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/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