linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Cc: linux-mm <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	 Zhansaya Bagdauletkyzy <zhansayabagdaulet@gmail.com>,
	Tyler Hicks <tyhicks@linux.microsoft.com>,
	 Hugh Dickins <hughd@google.com>, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH] selftest/vm: Fix ksm selftest to run with different NUMA topologies
Date: Mon, 13 Sep 2021 11:10:23 -0400	[thread overview]
Message-ID: <CA+CK2bA+QvaRYQ=r4J6AQrRsjFfauTBNtVscOvU0JE+Dwjfd6g@mail.gmail.com> (raw)
In-Reply-To: <20210913123040.278031-1-aneesh.kumar@linux.ibm.com>

On Mon, Sep 13, 2021 at 8:32 AM Aneesh Kumar K.V
<aneesh.kumar@linux.ibm.com> wrote:
>

Hi Aneesh,

Thank you for this fix. My comments below:

> Platforms can have non-contiguous NUMA nodes like below

Thanks for catching this.

> +static unsigned long get_next_mem_node(unsigned long node)



NUMA should be "int" not "unsigned long", especially as it is
confusing with negative numbers used in get_first_mem_node(). Also,
numa_max_node() returns int.

> +{
> +
> +       long node_size;
> +       unsigned long i;
> +       unsigned long max_node = numa_max_node();
> +       /*
> +        * start from node and find the next memory node
> +        */
> +restart:
> +       for (i = node + 1; i <= max_node; i++) {
> +               node_size = numa_node_size(i, NULL);
> +               if (node_size > 0)
> +                       return i;
> +       }
> +       node = -1;
> +       goto restart;
> +}

I would rewrite the above without goto, and possibility of stacking in
an infinite loop. Something like this should work:

       for (i = node + 1; i <= max_node + node; i++) {
               node_size = numa_node_size(i % (max_node + 1), NULL);
               if (node_size > 0)
                       break;
       }

        return i % (max_node + 1);

> +
> +static unsigned long get_first_mem_node(void)
> +{
> +       return get_next_mem_node(-1);

Next after the last node would make more sense:

return get_next_mem_node(numa_max_node());


> +}
> +
>  static int check_ksm_numa_merge(int mapping, int prot, int timeout, bool merge_across_nodes,
>                                 size_t page_size)
>  {
>         void *numa1_map_ptr, *numa2_map_ptr;
>         struct timespec start_time;
>         int page_count = 2;
> +       unsigned long first_node;

Please use int.

>
>         if (clock_gettime(CLOCK_MONOTONIC_RAW, &start_time)) {
>                 perror("clock_gettime");
> @@ -370,7 +395,7 @@ static int check_ksm_numa_merge(int mapping, int prot, int timeout, bool merge_a
>                 perror("NUMA support not enabled");
>                 return KSFT_SKIP;
>         }
> -       if (numa_max_node() < 1) {
> +       if (numa_num_configured_nodes() <= 1) {
>                 printf("At least 2 NUMA nodes must be available\n");
>                 return KSFT_SKIP;
>         }
> @@ -378,8 +403,9 @@ static int check_ksm_numa_merge(int mapping, int prot, int timeout, bool merge_a
>                 return KSFT_FAIL;
>
>         /* allocate 2 pages in 2 different NUMA nodes and fill them with the same data */
> -       numa1_map_ptr = numa_alloc_onnode(page_size, 0);
> -       numa2_map_ptr = numa_alloc_onnode(page_size, 1);
> +       first_node = get_first_mem_node();
> +       numa1_map_ptr = numa_alloc_onnode(page_size, first_node);
> +       numa2_map_ptr = numa_alloc_onnode(page_size, get_next_mem_node(first_node));

Thanks,
Pasha


  parent reply	other threads:[~2021-09-13 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 12:30 Aneesh Kumar K.V
2021-09-13 14:24 ` Tyler Hicks
2021-09-13 15:10 ` Pasha Tatashin [this message]
2021-09-13 16:31   ` Aneesh Kumar K.V
2021-09-13 18:36     ` Pasha Tatashin
2021-09-13 18:39 ` Zhansaya Bagdauletkyzy

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+CK2bA+QvaRYQ=r4J6AQrRsjFfauTBNtVscOvU0JE+Dwjfd6g@mail.gmail.com' \
    --to=pasha.tatashin@soleen.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=hughd@google.com \
    --cc=linux-mm@kvack.org \
    --cc=shuah@kernel.org \
    --cc=tyhicks@linux.microsoft.com \
    --cc=zhansayabagdaulet@gmail.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