DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stanislaw Kardach <kda@semihalf.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, Stanislaw Kardach <kda@semihalf.com>
Subject: [dpdk-dev] [PATCH 0/3] Increase test compatibility with PA IOVA
Date: Mon, 12 Apr 2021 12:06:42 +0200	[thread overview]
Message-ID: <20210412100645.668395-1-kda@semihalf.com> (raw)

While working in some scenarios where only RTE_IOVA_PA is available I've
noticed that some of the EAL tests are failing because of a totally
different reason than the test itself.
Namely the --no-huge flag and PA IOVA can't be used together and EAL
init fails warning about this.
This patchset tries to cleanup the --no-huge usage so that it doesn't
hide the real state of tests when RTE_IOVA_PA is used (i.e. on platforms
without IOMMU).

This means skipping the no-huge test as it is not supported by design and
removing no-huge usage on linux as it seems that it was previously used
with --no-shconf to increase the compatibility with FreeBSD. That is if
I'm not missing a bigger picture of using the --no-huge with --no-shconf
on non-FreeBSD platforms.

Stanislaw Kardach (3):
  test: disable no-huge test with PA IOVA
  test: disable no-huge where it's not necessary
  test: fix the -n unit test description

 app/test/test_eal_flags.c | 45 ++++++++++++++++++++++++++++-----------
 1 file changed, 32 insertions(+), 13 deletions(-)

-- 
2.27.0


             reply	other threads:[~2021-04-12 10:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 10:06 Stanislaw Kardach [this message]
2021-04-12 10:06 ` [dpdk-dev] [PATCH 1/3] test: disable no-huge test " Stanislaw Kardach
2021-04-12 10:06 ` [dpdk-dev] [PATCH 2/3] test: disable no-huge where it's not necessary Stanislaw Kardach
2021-04-12 10:06 ` [dpdk-dev] [PATCH 3/3] test: fix the -n unit test description Stanislaw Kardach

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=20210412100645.668395-1-kda@semihalf.com \
    --to=kda@semihalf.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.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).