From: Thomas Monjalon <thomas@monjalon.net>
To: dwilder <dwilder@us.ibm.com>
Cc: david.marchand@redhat.com, anatoly.burakov@intel.com,
aconole@redhat.com, maicolgabriel@hotmail.com,
ferruh.yigit@intel.com, arybchenko@solarflare.com, dev@dpdk.org,
ruifeng.wang@arm.com, drc@linux.vnet.ibm.com, wilder@us.ibm.com
Subject: Re: [dpdk-dev] [PATCH v1 1/2] devtools: allow test-null.sh to run on ppc64le
Date: Thu, 13 Feb 2020 23:17:59 +0100 [thread overview]
Message-ID: <3387752.bqPgKRP4r2@xps> (raw)
In-Reply-To: <c28b9d76f173bfb19b18866aff8259be@linux.vnet.ibm.com>
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?
next prev parent reply other threads:[~2020-02-13 22:18 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 [this message]
2020-02-13 23:23 ` dwilder
2020-02-14 13:22 ` David Marchand
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=3387752.bqPgKRP4r2@xps \
--to=thomas@monjalon.net \
--cc=aconole@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=arybchenko@solarflare.com \
--cc=david.marchand@redhat.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.