linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yang Shi <shy828301@gmail.com>
To: "Zach O'Keefe" <zokeefe@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux MM <linux-mm@kvack.org>,  Hugh Dickins <hughd@google.com>,
	Miaohe Lin <linmiaohe@huawei.com>
Subject: Re: [PATCH mm-unstable 1/4] mm/khugepaged: Use minimal bits to store num page < HPAGE_PMD_NR
Date: Wed, 20 Jul 2022 10:26:36 -0700	[thread overview]
Message-ID: <CAHbLzkrNN=M0qVqd37z-D=8GPgRmKpXGNwMyD_MHtc985sMjkA@mail.gmail.com> (raw)
In-Reply-To: <20220720140603.1958773-2-zokeefe@google.com>

On Wed, Jul 20, 2022 at 7:06 AM Zach O'Keefe <zokeefe@google.com> wrote:
>
> Minimally, node_load[] entries just need to be able to hold the maximum
> value of HPAGE_PMD_NR, which is compile-time defined per-arch based on
> PMD_SHIFT and PAGE_SHIFT.  node_load[] is only written either via memset(),
> or with via post-increment. struct collapse_control may be allocated
> via kmalloc() in other collapse contexts, and MAX_NUMNODES may be
> arbitrarily large. #define the underlying type of node_load[] based off
> HPAGE_PMD_NR to avoid excessive memory allocated for this struct.
>
> Fixes: 3b07f3bb225a ("mm/khugepaged: add struct collapse_control")
> Link: https://lore.kernel.org/linux-mm/Ys2CeIm%2FQmQwWh9a@google.com/
> Signed-off-by: Zach O'Keefe <zokeefe@google.com>

Reviewed-by: Yang Shi <shy828301@gmail.com>

> ---
>  mm/khugepaged.c | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
> index 69990dacde14..ecd28bfeab60 100644
> --- a/mm/khugepaged.c
> +++ b/mm/khugepaged.c
> @@ -92,8 +92,11 @@ struct collapse_control {
>         bool is_khugepaged;
>
>         /* Num pages scanned per node */
> -       int node_load[MAX_NUMNODES];
> -
> +#if HPAGE_PMD_ORDER < 16
> +       u16 node_load[MAX_NUMNODES];
> +#else
> +       u32 node_load[MAX_NUMNODES];
> +#endif
>         /* Last target selected in hpage_collapse_find_target_node() */
>         int last_target_node;
>  };
> --
> 2.37.0.170.g444d1eabd0-goog
>


  reply	other threads:[~2022-07-20 17:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-20 14:05 [PATCH mm-unstable 0/4] mm: fixes for userspace hugepage collapse, v7 Zach O'Keefe
2022-07-20 14:06 ` [PATCH mm-unstable 1/4] mm/khugepaged: Use minimal bits to store num page < HPAGE_PMD_NR Zach O'Keefe
2022-07-20 17:26   ` Yang Shi [this message]
2022-07-21  0:41   ` David Rientjes
2022-07-20 14:06 ` [PATCH mm-unstable 2/4] mm/khugepaged: consistently order cc->is_khugepaged and pte_* checks Zach O'Keefe
2022-07-20 17:27   ` Yang Shi
2022-07-20 19:09     ` Zach O'Keefe
2022-07-21  0:42   ` David Rientjes
2022-07-20 14:06 ` [PATCH mm-unstable 3/4] mm/khugepaged: delay computation of hpage boundaries until use Zach O'Keefe
2022-07-20 17:30   ` Yang Shi
2022-07-21  0:43   ` David Rientjes
2022-07-20 14:06 ` [PATCH mm-unstable 4/4] Revert "mm/madvise: add huge_memory:mm_madvise_collapse tracepoint" Zach O'Keefe
2022-07-20 17:30   ` Yang Shi
2022-07-21  0:43   ` David Rientjes

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='CAHbLzkrNN=M0qVqd37z-D=8GPgRmKpXGNwMyD_MHtc985sMjkA@mail.gmail.com' \
    --to=shy828301@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-mm@kvack.org \
    --cc=zokeefe@google.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