linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: rppt@kernel.org, mhocko@suse.com, vbabka@suse.cz,
	david@redhat.com,  quic_charante@quicinc.com,
	lizhe.67@bytedance.com,  linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH] mm/page_ext: init page_ext early if there are no deferred struct pages
Date: Wed, 18 Jan 2023 10:01:46 -0500	[thread overview]
Message-ID: <CA+CK2bCsYp839RVFLYTjx-NSwUxMJ9xG9Z=DDy7hgGn72+aMdw@mail.gmail.com> (raw)
In-Reply-To: <20230117171312.13bdb3b2673bdac3c93c2ab7@linux-foundation.org>

On Tue, Jan 17, 2023 at 8:13 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Tue, 17 Jan 2023 20:46:17 +0000 Pasha Tatashin <pasha.tatashin@soleen.com> wrote:
>
> > page_ext must be initialized after all struct pages are initialized.
> > Therefore, page_ext is initialized after page_alloc_init_late(), and
> > can optionally be initialized earlier via early_page_ext kernel
> > parameter which as a side effect also disables deferred struct pages.
> >
> > Allow to automatically init page_ext early when there are no deferred
> > struct pages in order to be able to use page_ext during kernel boot
> > and track for example page allocations early.
>
> Compilation blows up with CONFIG_PAGE_EXTENSION=n.  I did

Thanks, I will update the patch and send it soon.

Pasha


      reply	other threads:[~2023-01-18 15:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 20:46 Pasha Tatashin
2023-01-18  1:13 ` Andrew Morton
2023-01-18 15:01   ` Pasha Tatashin [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='CA+CK2bCsYp839RVFLYTjx-NSwUxMJ9xG9Z=DDy7hgGn72+aMdw@mail.gmail.com' \
    --to=pasha.tatashin@soleen.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lizhe.67@bytedance.com \
    --cc=mhocko@suse.com \
    --cc=quic_charante@quicinc.com \
    --cc=rppt@kernel.org \
    --cc=vbabka@suse.cz \
    /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