linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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 v3 0/5] memblock tests: add tests for memblock_alloc_exact_nid_raw
Date: Mon, 31 Oct 2022 10:43:24 +0200	[thread overview]
Message-ID: <Y1+KrIyFAOZ/oNqp@kernel.org> (raw)
In-Reply-To: <20221031050006.GA15612@sophie>

Hi Rebecca,

On Mon, Oct 31, 2022 at 12:00:06AM -0500, Rebecca Mckeever wrote:
> Hi Mike,
> 
> I noticed that the memblock tree has been updated since I sent this
> patch set. Do you want me to send an updated patch set applied on top of
> the current tree?

No need, the only actual conflict is in TODO, I'll fix it while applying.
 
> On Wed, Oct 19, 2022 at 01:34:07PM -0500, 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.
> > 
> > ---
> > Changelog
> > 
> > v1 -> v2
> > PATCH 0:
> > - Add missing memblock_alloc_exact_nid_raw to subject line
> > 
> > v2 -> v3
> > Based on feedback from David Hildenbrand:
> > PATCH 1:
> > - alloc_nid_api.c, alloc_nid_api.h, common.h:
> >     + Add TEST_F_EXACT flag so that tests in alloc_nid_api.c can be run
> >       with that flag to test memblock_alloc_exact_nid_raw()
> > - alloc_exact_nid_api.c:
> >     + Update to run range tests in alloc_nid_api.c with TEST_F_EXACT flag
> >       instead of using a separate set of tests
> > - alloc_nid_api.c:
> >     + Rename tests and other functions by removing "_try" so that the
> >       function names are general enough to refer to any of the
> >       memblock_alloc_*nid*() functions of the memblock API
> > ---
> > 
> > Rebecca Mckeever (5):
> >   memblock tests: introduce range tests for memblock_alloc_exact_nid_raw
> >   memblock tests: add top-down NUMA tests for
> >     memblock_alloc_exact_nid_raw
> >   memblock tests: add bottom-up NUMA tests for
> >     memblock_alloc_exact_nid_raw
> >   memblock tests: add generic NUMA tests for
> >     memblock_alloc_exact_nid_raw
> >   memblock tests: remove completed TODO item
> > 
> >  tools/testing/memblock/Makefile               |    2 +-
> >  tools/testing/memblock/TODO                   |    7 +-
> >  tools/testing/memblock/main.c                 |    2 +
> >  .../memblock/tests/alloc_exact_nid_api.c      | 1113 +++++++++++++++++
> >  .../memblock/tests/alloc_exact_nid_api.h      |   25 +
> >  tools/testing/memblock/tests/alloc_nid_api.c  |  542 ++++----
> >  tools/testing/memblock/tests/alloc_nid_api.h  |    1 +
> >  tools/testing/memblock/tests/common.h         |    2 +
> >  8 files changed, 1425 insertions(+), 269 deletions(-)
> >  create mode 100644 tools/testing/memblock/tests/alloc_exact_nid_api.c
> >  create mode 100644 tools/testing/memblock/tests/alloc_exact_nid_api.h
> > 
> > -- 
> > 2.25.1
> > 
> Thanks,
> Rebecca

-- 
Sincerely yours,
Mike.


  reply	other threads:[~2022-10-31  8:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 18:34 Rebecca Mckeever
2022-10-19 18:34 ` [PATCH v3 1/5] memblock tests: introduce range " Rebecca Mckeever
2022-10-31 10:28   ` David Hildenbrand
2022-11-03  4:02     ` Rebecca Mckeever
2022-10-19 18:34 ` [PATCH v3 2/5] memblock tests: add top-down NUMA " Rebecca Mckeever
2022-10-31 10:36   ` David Hildenbrand
2022-10-19 18:34 ` [PATCH v3 3/5] memblock tests: add bottom-up " Rebecca Mckeever
2022-10-31 10:39   ` David Hildenbrand
2022-10-19 18:34 ` [PATCH v3 4/5] memblock tests: add generic " Rebecca Mckeever
2022-10-31 12:42   ` David Hildenbrand
2022-10-19 18:34 ` [PATCH v3 5/5] memblock tests: remove completed TODO item Rebecca Mckeever
2022-10-31  5:00 ` [PATCH v3 0/5] memblock tests: add tests for memblock_alloc_exact_nid_raw Rebecca Mckeever
2022-10-31  8:43   ` Mike Rapoport [this message]
2022-10-31 12:43 ` David Hildenbrand

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=Y1+KrIyFAOZ/oNqp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox