DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: David Wilder <dwilder@us.ibm.com>,
	"Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: Aaron Conole <aconole@redhat.com>,
	Michael Santana <maicolgabriel@hotmail.com>,
	 Thomas Monjalon <thomas@monjalon.net>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	Andrew Rybchenko <arybchenko@solarflare.com>, dev <dev@dpdk.org>,
	 "Ruifeng Wang (Arm Technology China)" <ruifeng.wang@arm.com>,
	David Christensen <drc@linux.vnet.ibm.com>,
	 Jerin Jacob <jerinjacobk@gmail.com>,
	David Wilder <wilder@us.ibm.com>
Subject: Re: [dpdk-dev] [PATCH v4 0/4] add travis ci support for ppc64le
Date: Thu, 25 Mar 2021 16:06:09 +0100	[thread overview]
Message-ID: <CAJFAV8wdtnt4Qc8PVYVT9vGjHE6Lhj0fg8qBiSJRJg+3V5u7nw@mail.gmail.com> (raw)
In-Reply-To: <20200402171241.13258-1-dwilder@us.ibm.com>

On Thu, Apr 2, 2020 at 7:13 PM David Wilder <dwilder@us.ibm.com> wrote:
>
> This patch series adds Travis gcc compilation jobs and unit testing
> for ppc64le.  Limitations for ppc64le are similar to arm64 (see commit
> 31bb45bcfd).
>
> 1. Only gcc builds are supported on ppc64le.
> 2. Hugepages are not available in the ppc64le Travis environment.
> 3. Memory requirements are larger for ppc64le due to a higher
>    RTE_MAX_LCORE value.
>
> V2: Insures iova-mode is VA when --no-huge is selected.
>     Removed setting of --iova-mode=VA in test-null.sh.
> V3: Refactor ppc64le changes on top of David Marchand's
>     Patch series: "Reorganise Travis jobs"
>     http://mails.dpdk.org/archives/dev/2020-February/158231.html
> V4: Adding unit testing.
>     Updated eal/linux: patch to force PA mode when --huge-page is used.
>     This should be a more straightforward solution than my V3 patch.
>
> A Travis build with theses patches can be found here:
> https://travis-ci.org/github/djlwilder/dpdk/builds/670214578
> David Wilder (4):
>   eal/linux: force iova-mode va with no-huge option
>   devtools: allow test-null.sh to run on ppc64le
>   ci: add travis ci support for native ppc64le
>   ci: enable unit test for ppc64le
>

Is this series still applicable?
The changes on EAL did not get a review.


-- 
David Marchand


  parent reply	other threads:[~2021-03-25 15:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-02 17:12 David Wilder
2020-04-02 17:12 ` [dpdk-dev] [PATCH v4 1/4] eal/linux: force iova-mode va with no-huge option David Wilder
2020-04-02 17:12 ` [dpdk-dev] [PATCH v4 2/4] devtools: allow test-null.sh to run on ppc64le David Wilder
2020-04-02 17:12 ` [dpdk-dev] [PATCH v4 3/4] ci: add travis ci support for native ppc64le David Wilder
2020-04-02 17:12 ` [dpdk-dev] [PATCH v4 4/4] ci: enable unit test for ppc64le David Wilder
2021-03-25 15:06 ` David Marchand [this message]
2021-04-15 14:45 ` [dpdk-dev] [PATCH v4 0/4] add travis ci support " Christian Ehrhardt
2021-04-19 12:22   ` Luca Boccassi

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=CAJFAV8wdtnt4Qc8PVYVT9vGjHE6Lhj0fg8qBiSJRJg+3V5u7nw@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --cc=anatoly.burakov@intel.com \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=dwilder@us.ibm.com \
    --cc=ferruh.yigit@intel.com \
    --cc=jerinjacobk@gmail.com \
    --cc=maicolgabriel@hotmail.com \
    --cc=ruifeng.wang@arm.com \
    --cc=thomas@monjalon.net \
    --cc=wilder@us.ibm.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;
as well as URLs for NNTP newsgroup(s).