[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y2iz7yBakBfGa5VR@kernel.org>
Date: Mon, 7 Nov 2022 09:29:51 +0200
From: Mike Rapoport <rppt@...nel.org>
To: Rebecca Mckeever <remckee0@...il.com>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
David Hildenbrand <david@...hat.com>
Subject: Re: [PATCH v4 0/5] memblock tests: add tests for
memblock_alloc_exact_nid_raw
On Mon, Nov 07, 2022 at 12:28:04AM -0600, Rebecca Mckeever wrote:
> These patches add tests for memblock_alloc_exact_nid_raw(). There are two
> sets of tests: range tests and NUMA tests. The range tests use a normal
> (i.e., UMA) simulated physical memory and set the nid to NUMA_NO_NODE. The
> NUMA tests use a simulated physical memory that is set up with multiple
> NUMA nodes. Additionally, most of the NUMA tests set nid != NUMA_NO_NODE.
>
> For the range tests, the TEST_F_EXACT flag is used to run the same set of
> range tests used for memblock_alloc_try_nid_raw(). The NUMA tests have the
> same setup as the corresponding test for memblock_alloc_try_nid_raw(), but
> several of the memblock_alloc_exact_nid_raw() tests fail to allocate
> memory in setups where the memblock_alloc_try_nid_raw() test would
> allocate memory. Also, some memblock_alloc_exact_nid_raw() tests drop the
> lower limit of the requested range in order to allocate within the
> requested node, but the same setup in a memblock_alloc_try_nid_raw() test
> allocates within the requested range.
Applied, thanks!
--
Sincerely yours,
Mike.
Powered by blists - more mailing lists