From: Andrew Morton <akpm@linux-foundation.org>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: 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 v2] mm/page_ext: Do not allocate space for page_ext->flags if not needed
Date: Thu, 12 Jan 2023 13:29:57 -0800 [thread overview]
Message-ID: <20230112132957.6cb97c2afad17cdeb06fcd10@linux-foundation.org> (raw)
In-Reply-To: <20230112153348.3202173-1-pasha.tatashin@soleen.com>
On Thu, 12 Jan 2023 15:33:48 +0000 Pasha Tatashin <pasha.tatashin@soleen.com> wrote:
> There is 8 byte page_ext->flags field allocated per page whenever
> CONFIG_PAGE_EXTENSION is enabled. However, not every user of page_ext
> uses flags. Therefore, check whether flags is needed at least by one
> user and if so allocate space for it.
>
> For example when page_table_check is enabled, on a machine with 128G
> of memory before the fix:
>
> [ 2.244288] allocated 536870912 bytes of page_ext
> after the fix:
> [ 2.160154] allocated 268435456 bytes of page_ext
>
Looks nice.
Does it work correctly with early_page_ext=1?
> --- a/include/linux/page_ext.h
> +++ b/include/linux/page_ext.h
> @@ -12,10 +12,14 @@ struct page_ext_operations {
> size_t size;
> bool (*need)(void);
> void (*init)(void);
> + bool using_shared_ext_flags;
> };
Seems overly complicated. Can we change the three early-init
functions such as setup_early_page_ext() to simply set some global bool
flag?
> #endif
> };
>
> -unsigned long page_ext_size = sizeof(struct page_ext);
> +unsigned long page_ext_size;
>
> static unsigned long total_usage;
> static struct page_ext *lookup_page_ext(const struct page *page);
> @@ -105,6 +106,15 @@ static bool __init invoke_need_callbacks(void)
> int entries = ARRAY_SIZE(page_ext_ops);
> bool need = false;
>
> + for (i = 0; i < entries; i++) {
> + if (page_ext_ops[i]->need && page_ext_ops[i]->need()) {
I don't think this (or the below) need to check for ->need==NULL?
> + if (page_ext_ops[i]->using_shared_ext_flags) {
> + page_ext_size = sizeof(struct page_ext);
> + break;
> + }
> + }
> + }
> +
> for (i = 0; i < entries; i++) {
> if (page_ext_ops[i]->need && page_ext_ops[i]->need()) {
> page_ext_ops[i]->offset = page_ext_size;
next prev parent reply other threads:[~2023-01-12 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 15:33 Pasha Tatashin
2023-01-12 21:29 ` Andrew Morton [this message]
2023-01-13 14:44 ` Pasha Tatashin
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=20230112132957.6cb97c2afad17cdeb06fcd10@linux-foundation.org \
--to=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=pasha.tatashin@soleen.com \
--cc=quic_charante@quicinc.com \
--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