DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: "thomas@monjalon.net" <thomas@monjalon.net>,
	"yskoh@mellanox.com" <yskoh@mellanox.com>
Cc: "shahafs@mellanox.com" <shahafs@mellanox.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] config: add Mellanox BlueField ARMv8 SoC
Date: Wed, 9 Jan 2019 09:43:38 +0000	[thread overview]
Message-ID: <065ae8b5a423d4823b60d1759379c7935d9dda0e.camel@marvell.com> (raw)
In-Reply-To: <20190109093201.40603-1-yskoh@mellanox.com>

On Wed, 2019-01-09 at 01:32 -0800, Yongseok Koh wrote:
> BlueField is Mellanox's new SoC based on ARMv8. BlueField integrates
> Mellanox ConnectX-5 interconnect and Cortex-A72 cores into a single
> device.
> 
> http://www.mellanox.com/page/products_dyn?product_family=256&mtag=soc_overview
> 
> Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
> ---
> 
> This patch should be applied after
> 	"config: gather options for dlopen mlx dependency" [1]
> 
> [1] http://patches.dpdk.org/patch/49502
> 
>  config/defconfig_arm64-bluefield-linuxapp-gcc | 24 

Please add meson support together in this patch.


> ++++++++++++++++++++++++
>  1 file changed, 24 insertions(+)
>  create mode 100644 config/defconfig_arm64-bluefield-linuxapp-gcc
> 
> diff --git a/config/defconfig_arm64-bluefield-linuxapp-gcc
> b/config/defconfig_arm64-bluefield-linuxapp-gcc
> new file mode 100644
> index 0000000000..8494a33641
> --- /dev/null
> +++ b/config/defconfig_arm64-bluefield-linuxapp-gcc
> @@ -0,0 +1,24 @@
> +# SPDX-License-Identifier: BSD-3-Clause
> +# Copyright 2019 Mellanox Technologies, Ltd
> +#
> +
> +#include "defconfig_arm64-armv8a-linuxapp-gcc"
> +
> +# Mellanox BlueField
> +CONFIG_RTE_ARCH_ARM_TUNE="cortex-a72"
> +
> +CONFIG_RTE_MAX_NUMA_NODES=1
> +CONFIG_RTE_CACHE_LINE_SIZE=64
> +
> +# UMA architecture
> +CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=n
> +CONFIG_RTE_LIBRTE_VHOST_NUMA=n
> +
> +CONFIG_RTE_EAL_IGB_UIO=n
> +CONFIG_RTE_EAL_VFIO=n
> +CONFIG_RTE_KNI_KMOD=n

Does this SoC has external PCIe support? If so, VFIO may be required.


> +
> +# PMD for ConnectX-5
> +CONFIG_RTE_LIBRTE_MLX5_PMD=y
> +CONFIG_RTE_LIBRTE_MLX5_DEBUG=n
> +CONFIG_RTE_IBVERBS_LINK_DLOPEN=n

  reply	other threads:[~2019-01-09  9:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09  9:32 Yongseok Koh
2019-01-09  9:43 ` Jerin Jacob Kollanukkaran [this message]
2019-01-09  9:51   ` Yongseok Koh
2019-01-09 10:00     ` [dpdk-dev] [EXT] " Jerin Jacob Kollanukkaran
2019-01-09 12:34 ` [dpdk-dev] [PATCH v2] " Yongseok Koh
2019-01-09 13:08   ` Jerin Jacob Kollanukkaran
2019-01-10 18:39 ` [dpdk-dev] [PATCH v3] " Yongseok Koh
2019-01-11  2:47   ` Gavin Hu (Arm Technology China)
2019-01-11  7:50     ` Yongseok Koh
2019-01-14  6:12   ` Honnappa Nagarahalli
2019-01-14  6:13     ` Honnappa Nagarahalli
2019-01-14 10:11       ` Yongseok Koh
2019-01-14 10:25         ` Thomas Monjalon
2019-01-14 10:47   ` Thomas Monjalon

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=065ae8b5a423d4823b60d1759379c7935d9dda0e.camel@marvell.com \
    --to=jerinj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=shahafs@mellanox.com \
    --cc=thomas@monjalon.net \
    --cc=yskoh@mellanox.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).