DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: dwilder <dwilder@us.ibm.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	"Burakov, Anatoly" <anatoly.burakov@intel.com>,
	 Aaron Conole <aconole@redhat.com>,
	Michael Santana <maicolgabriel@hotmail.com>,
	"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>,
	 David Wilder <wilder@us.ibm.com>
Subject: Re: [dpdk-dev] [PATCH v1 1/2] devtools: allow test-null.sh to run on ppc64le
Date: Fri, 14 Feb 2020 14:22:28 +0100	[thread overview]
Message-ID: <CAJFAV8yMTqSe=1AnQGngax1LHEjCXwCLwUu-HCphQ4acgo_Qiw@mail.gmail.com> (raw)
In-Reply-To: <29fa0202af95822277276caccbfcf967@linux.vnet.ibm.com>

On Fri, Feb 14, 2020 at 12:22 AM dwilder <dwilder@us.ibm.com> wrote:
>
> On 2020-02-13 14:17, Thomas Monjalon wrote:
> > 13/02/2020 21:58, dwilder:
> >> On 2020-02-13 12:32, Thomas Monjalon wrote:
> >> > 13/02/2020 21:24, David Wilder:
> >> >> - The --no-huge option requires iova-mode=VA.
> >> >>   On ppc64le iova-mode defaults to PA therefor
> >> >>   VA mode must be explicitly set.
> >> >
> >> > Should we make VA mode automatic when using --no-huge?
> >> > Should we log an error message when using --no-huge with PA mode?
> >>
> >> Logging a messages sounds like a good idea.  Ignoring the users
> >> request
> >> of iova-mode=PA (in the case of x86) and just switching modes would be
> >> bad.
> >
> > Yes, I mean for ppc64, if --no-huge is specified,
> > would you like to change the default to VA mode?
>
> OK, that would be better.
> I will switch to VA when --no-huge is set (ppc64 only).

With no-huge, we can't ensure the physical addresses won't change
(might be different if we locked the pages in memory... but not
possible and/or not handled in eal afaics).
This limitation is generic, not arch specific.


> Add log messages if PA is selected with --no-huge (all arches).

-- 
David Marchand


  reply	other threads:[~2020-02-14 13:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 20:24 [dpdk-dev] [PATCH v1 0/2] add travis ci support for ppc64le David Wilder
2020-02-13 20:24 ` [dpdk-dev] [PATCH v1 1/2] devtools: allow test-null.sh to run on ppc64le David Wilder
2020-02-13 20:32   ` Thomas Monjalon
2020-02-13 20:58     ` dwilder
2020-02-13 22:17       ` Thomas Monjalon
2020-02-13 23:23         ` dwilder
2020-02-14 13:22           ` David Marchand [this message]
2020-02-13 20:24 ` [dpdk-dev] [PATCH v1 2/2] ci: add travis ci support for native ppc64le David Wilder

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='CAJFAV8yMTqSe=1AnQGngax1LHEjCXwCLwUu-HCphQ4acgo_Qiw@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=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).