From: Yongseok Koh <yskoh@mellanox.com>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>,
Shahaf Shuler <shahafs@mellanox.com>,
"jerinj@marvell.com" <jerinj@marvell.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v3] config: add Mellanox BlueField ARMv8 SoC
Date: Mon, 14 Jan 2019 10:11:53 +0000 [thread overview]
Message-ID: <2CE6DB92-BEB8-439F-9C94-6C7DFAD51978@mellanox.com> (raw)
In-Reply-To: <AM6PR08MB36721803AFEFBC50A4259B7998800@AM6PR08MB3672.eurprd08.prod.outlook.com>
> On Jan 13, 2019, at 10:13 PM, Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com> wrote:
>
> Similarly, the commit heading subject line also needs to change.
>
>>
>>>
>>> BlueField is Mellanox's new SoC based on ARMv8. BlueField integrates
>> ^^^^^^ Above should be
>> changed to armv8
Good to know that, thanks, Honnappa.
Thomas, will you take care of it when you merge (hope you will :-)?
Shall I send out a new version?
Thanks,
Yongseok
>>
>>> Mellanox ConnectX-5 interconnect and Cortex-A72 cores into a single device.
>>>
>>>
>> http://www.mellanox.com/page/products_dyn?product_family=256&mtag=s
>>> oc_overview
>>>
>>> Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
>>> ---
>>>
>>> v3:
>>> * remove redundant mlx5 config items
>>>
>>> v2:
>>> * remove config items which can be used for external PCIe device
>>>
>>> config/defconfig_arm64-bluefield-linuxapp-gcc | 18 ++++++++++++++++++
>>> 1 file changed, 18 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..dd252c0e47
>>> --- /dev/null
>>> +++ b/config/defconfig_arm64-bluefield-linuxapp-gcc
>>> @@ -0,0 +1,18 @@
>>> +# 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
>>> +
>>> +# PMD for ConnectX-5
>>> +CONFIG_RTE_LIBRTE_MLX5_PMD=y
>>> --
>>> 2.11.0
>
next prev parent reply other threads:[~2019-01-14 10:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 9:32 [dpdk-dev] [PATCH] " Yongseok Koh
2019-01-09 9:43 ` Jerin Jacob Kollanukkaran
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 [this message]
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=2CE6DB92-BEB8-439F-9C94-6C7DFAD51978@mellanox.com \
--to=yskoh@mellanox.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=nd@arm.com \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.net \
/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).