All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: David Wilder <dwilder@us.ibm.com>
Cc: dev@dpdk.org, pradeep@us.ibm.com, drc@ibm.com
Subject: Re: [dpdk-dev] [PATCH] meson: Update flags and values for ppc_64
Date: Mon, 27 May 2019 10:41:16 +0100	[thread overview]
Message-ID: <20190527094116.GA425@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20190524160404.15896-1-dwilder@us.ibm.com>

On Fri, May 24, 2019 at 09:04:04AM -0700, David Wilder wrote:
> Setting RTE_MAX_LCORE to reflect the largest available configuration.
> Adding defines for missing RTE_MACHINE_CPUFLAGs.
> 
> Signed-off-by: David Wilder <dwilder@us.ibm.com>
> ---
>  config/ppc_64/meson.build | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/config/ppc_64/meson.build b/config/ppc_64/meson.build
> index 7ceae1d..0e65f9d 100644
> --- a/config/ppc_64/meson.build
> +++ b/config/ppc_64/meson.build
> @@ -8,6 +8,8 @@ dpdk_conf.set('RTE_ARCH', 'ppc_64')
>  dpdk_conf.set('RTE_ARCH_PPC_64', 1)
>  
>  # overrides specific to ppc64
> -dpdk_conf.set('RTE_MAX_LCORE', 256)
> +dpdk_conf.set('RTE_MAX_LCORE', 1536)
>  dpdk_conf.set('RTE_MAX_NUMA_NODES', 32)
>  dpdk_conf.set('RTE_CACHE_LINE_SIZE', 128)
> +dpdk_conf.set('RTE_MACHINE_CPUFLAG_ALTIVEC', 1)
> +dpdk_conf.set('RTE_MACHINE_CPUFLAG_VSX', 1)
> -- 

Acked-by: Bruce Richardson <bruce.richardson@intel.com>

  reply	other threads:[~2019-05-27  9:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-24 16:04 [dpdk-dev] [PATCH] meson: Update flags and values for ppc_64 David Wilder
2019-05-27  9:41 ` Bruce Richardson [this message]
2019-06-03 22:30   ` Thomas Monjalon
2019-06-04 20:25     ` dwilder
2019-06-04 21:04       ` Thomas Monjalon
2019-06-04 21:13         ` dwilder

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=20190527094116.GA425@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=drc@ibm.com \
    --cc=dwilder@us.ibm.com \
    --cc=pradeep@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.