From: Mike Rapoport <rppt@kernel.org>
To: Rebecca Mckeever <remckee0@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH v6 0/4] memblock tests: add NUMA tests for memblock_alloc_try_nid*
Date: Sun, 18 Sep 2022 10:32:05 +0300 [thread overview]
Message-ID: <YybJdXgUm1csEsWj@kernel.org> (raw)
In-Reply-To: <cover.1663046060.git.remckee0@gmail.com>
On Tue, Sep 13, 2022 at 12:21:08AM -0500, Rebecca Mckeever wrote:
> These patches add additional tests for memblock_alloc_try_nid() and
> memblock_alloc_try_nid_raw() that use a simulated physical
> memory that is set up with multiple NUMA nodes. Additionally, most of
> these tests set nid != NUMA_NO_NODE.
>
> To set up a simulated physical memory with multiple NUMA nodes, patch 1
> introduces setup_numa_memblock(). This function uses a previously
> allocated dummy physical memory. It can be used in place of
> setup_memblock() in tests that need to simulate a NUMA system.
>
> These tests are run twice, once for memblock_alloc_try_nid() and once
> for memblock_alloc_try_nid_raw(), so that both functions are tested with
> the same set of tests. When the tests run memblock_alloc_try_nid(), they
> test that the entire memory region is zero. When the tests run
> memblock_alloc_try_nid_raw(), they test that the entire memory region is
> nonzero.
>
> Rebecca Mckeever (4):
> memblock tests: add simulation of physical memory with multiple NUMA
> nodes
> memblock tests: add top-down NUMA tests for memblock_alloc_try_nid*
> memblock tests: add bottom-up NUMA tests for memblock_alloc_try_nid*
> memblock tests: add generic NUMA tests for memblock_alloc_try_nid*
>
> .../testing/memblock/scripts/Makefile.include | 2 +-
> tools/testing/memblock/tests/alloc_nid_api.c | 1466 ++++++++++++++++-
> tools/testing/memblock/tests/alloc_nid_api.h | 16 +
> tools/testing/memblock/tests/common.c | 31 +
> tools/testing/memblock/tests/common.h | 22 +-
> 5 files changed, 1524 insertions(+), 13 deletions(-)
Applied, thanks!
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2022-09-18 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 5:21 [PATCH v6 0/4] memblock tests: add NUMA tests for memblock_alloc_try_nid* Rebecca Mckeever
2022-09-13 5:21 ` [PATCH v6 1/4] memblock tests: add simulation of physical memory with multiple NUMA nodes Rebecca Mckeever
2022-09-13 5:21 ` [PATCH v6 2/4] memblock tests: add top-down NUMA tests for memblock_alloc_try_nid* Rebecca Mckeever
2022-09-13 5:21 ` [PATCH v6 3/4] memblock tests: add bottom-up " Rebecca Mckeever
2022-09-13 5:21 ` [PATCH v6 4/4] memblock tests: add generic " Rebecca Mckeever
2022-09-18 7:32 ` Mike Rapoport [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=YybJdXgUm1csEsWj@kernel.org \
--to=rppt@kernel.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=remckee0@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.