DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: dev@dpdk.org
Cc: stable@dpdk.org, david.marchand@redhat.com,
	dmitry.kozliuk@gmail.com, stephen@networkplumber.org,
	Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: [PATCH v2 0/2] Enable the lcores test on Windows instead of skipping it.
Date: Fri, 16 Dec 2022 09:16:38 -0800	[thread overview]
Message-ID: <1671211000-14856-1-git-send-email-roretzla@linux.microsoft.com> (raw)
In-Reply-To: <1670287169-15325-1-git-send-email-roretzla@linux.microsoft.com>

Two bugs are fixed to allow this test to build, run & pass.
  * Mark memory configuration complete during rte_eal_init()
  * Use rte thread api to get a proper implementation of thread join.

v2:
  * update commit message to clarify why this test is beneficial on Windows.
  * add missing Fixes tag

Tyler Retzlaff (2):
  eal: add missing call marking memory config complete
  test: enable lcores test on Windows

 app/test/test_lcores.c | 28 +++++++++++++---------------
 lib/eal/windows/eal.c  |  3 +++
 2 files changed, 16 insertions(+), 15 deletions(-)

-- 
1.8.3.1


  parent reply	other threads:[~2022-12-16 17:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06  0:39 [PATCH 0/2] enable lcores test on Windows Tyler Retzlaff
2022-12-06  0:39 ` [PATCH 1/2] eal: add missing call marking memory config complete Tyler Retzlaff
2022-12-14 16:52   ` Stephen Hemminger
2022-12-15  9:59   ` David Marchand
2022-12-15 18:07     ` Tyler Retzlaff
2022-12-06  0:39 ` [PATCH 2/2] test: enable lcores test on Windows Tyler Retzlaff
2022-12-14 16:53   ` Stephen Hemminger
2022-12-12 20:36 ` [PATCH 0/2] " Tyler Retzlaff
2022-12-16 17:16 ` Tyler Retzlaff [this message]
2022-12-16 17:16   ` [PATCH v2 1/2] eal: add missing call marking memory config complete Tyler Retzlaff
2022-12-16 17:16   ` [PATCH v2 2/2] test: enable lcores test on Windows Tyler Retzlaff
2022-12-21 15:03   ` [PATCH v2 0/2] Enable the lcores test on Windows instead of skipping it David Marchand

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=1671211000-14856-1-git-send-email-roretzla@linux.microsoft.com \
    --to=roretzla@linux.microsoft.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    /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;
as well as URLs for NNTP newsgroup(s).