linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: David Hildenbrand <david@redhat.com>
Cc: Ryan Roberts <ryan.roberts@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Yin Fengwei <fengwei.yin@intel.com>, Yu Zhao <yuzhao@google.com>,
	Yang Shi <shy828301@gmail.com>,
	"Huang, Ying" <ying.huang@intel.com>, Zi Yan <ziy@nvidia.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v1 1/3] mm: Allow deferred splitting of arbitrary large anon folios
Date: Mon, 17 Jul 2023 17:17:18 +0100	[thread overview]
Message-ID: <ZLVpjhAvk/nAquiY@casper.infradead.org> (raw)
In-Reply-To: <ZLVkUlQXmPH1BXEx@casper.infradead.org>

On Mon, Jul 17, 2023 at 04:54:58PM +0100, Matthew Wilcox wrote:
> Those are page->flags and page->compound_head for the third page in
> the folio.  They don't really need a name; nothing refers to them,
> but it's important that space not be reused ;-)
> 
> This is slightly different from _flags_1; we do have some flags which
> reuse the bits (they're labelled as PF_SECOND).  Right now, it's only
> PG_has_hwpoisoned, but we used to have PG_double_map.  Others may arise.

Sorry, this was incomplete.  We do still have per-page flags!  HWPoison
is the obvious one, but PG_head is per-page (... think about it ...)
PG_anon_exclusive is actually per-page.

Most of the flags labelled as PF_ANY are mislabelled.  PG_private and
PG_private2 are never set/cleared/tested on tail pages.  PG_young and
PG_idle are only ever tested on the head page, but some code incorrectly
sets them on tail pages, where those bits are ignored.  I tried to fix
that a while ago, but the patch was overlooked and I couldn't be bothered
to try all that hard.  I have no clue about PG_vmemmap_self_hosted.
I think PG_isolated is probably never set on compound pages.
PG_owner_priv_1 is a disaster, as you might expect.


  reply	other threads:[~2023-07-17 16:17 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 14:31 [PATCH v1 0/3] Optimize large folio interaction with deferred split Ryan Roberts
2023-07-17 14:31 ` [PATCH v1 1/3] mm: Allow deferred splitting of arbitrary large anon folios Ryan Roberts
2023-07-17 15:30   ` Matthew Wilcox
2023-07-17 15:41     ` Ryan Roberts
2023-07-17 15:43       ` David Hildenbrand
2023-07-17 15:54         ` Matthew Wilcox
2023-07-17 16:17           ` Matthew Wilcox [this message]
2023-07-17 16:55           ` David Hildenbrand
2023-07-17 15:42   ` David Hildenbrand
2023-07-17 16:01     ` Ryan Roberts
2023-07-17 16:48       ` David Hildenbrand
2023-07-18  8:58         ` Ryan Roberts
2023-07-18  9:08           ` David Hildenbrand
2023-07-18  9:33             ` Ryan Roberts
2023-07-17 14:31 ` [PATCH v1 2/3] mm: Implement folio_remove_rmap_range() Ryan Roberts
2023-07-17 15:07   ` Matthew Wilcox
2023-07-17 15:49     ` Ryan Roberts
2023-07-17 15:56       ` Matthew Wilcox
2023-07-17 15:09   ` Zi Yan
2023-07-17 15:51     ` Ryan Roberts
2023-07-17 15:53       ` Zi Yan
2023-07-18  1:14   ` Yin Fengwei
2023-07-18  6:22   ` Huang, Ying
2023-07-18  9:51     ` Ryan Roberts
2023-07-18  7:12   ` Huang, Ying
2023-07-18 10:02     ` Ryan Roberts
2023-07-17 14:31 ` [PATCH v1 3/3] mm: Batch-zap large anonymous folio PTE mappings Ryan Roberts
2023-07-17 15:25   ` Zi Yan
2023-07-17 15:55     ` Ryan Roberts
2023-07-17 16:15       ` Zi Yan
2023-07-18 10:19         ` Ryan Roberts
2023-07-18 14:01           ` Zi Yan
2023-07-17 23:27   ` Yin Fengwei
2023-07-18 10:27     ` Ryan Roberts

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=ZLVpjhAvk/nAquiY@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=fengwei.yin@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ryan.roberts@arm.com \
    --cc=shy828301@gmail.com \
    --cc=ying.huang@intel.com \
    --cc=yuzhao@google.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