From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id BB6F4374C for ; Wed, 8 May 2019 10:27:59 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 320952217D; Wed, 8 May 2019 04:27:59 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 08 May 2019 04:27:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=azhnOVIDkJRGgeS26frChPunKpQGbbBWsci5Lqm4B8k=; b=HEPu1TWrkJ2f boToTiZ8M7x4ppIs0zl7JJYQl0d416DuT4RJyeJpgR182R25gXmdVXjSFsrcCz+r 3MSgRUv0ejEgjbsPWnDfGlOIP15tJ0CJ63YCOnaAVVn8M2maaGfP6RoKD2VaAsAR 8tgneG3dnnrenlXp7Izrxata87mg+Sk= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=azhnOVIDkJRGgeS26frChPunKpQGbbBWsci5Lqm4B 8k=; b=JwR4pL5n0LQdf+myLhs4B3r0ibCvLIqKCA9pTz87lEO9hBc71NHENuHVA DkyOAohy7TCmJmbhr1PTy9DG8QdWGHyTWIkNGzgwz/WUzT4h8TKCUQAU5rvLzXfi R302hykLaUs9SyMhXz+UhmOunsCrJufrrQUhbfmUVvihcW/gvuMp4WPjwL/TTbuu 9afJ9IyErLocSFT7MORbhMk/WL9p0/OkIc5jkakGYOWwQ5SyyRU26VbFrnIgOtzk tKPmEpr03SpCByt0tzgY14jvoM3d/Nv6eMy/JbS2fdN9YFZXeMqTbwmbfnYEXUMP h65YuLCZpvieHqXyWclqCFR25G/8A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrkeefgddtudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucffoh hmrghinhepmhgvlhhlrghnohigrdgtohhmnecukfhppeejjedrudefgedrvddtfedrudek geenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnh gvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id B9409103CA; Wed, 8 May 2019 04:27:57 -0400 (EDT) From: Thomas Monjalon To: Yongseok Koh Cc: dev@dpdk.org, jerinj@marvell.com, shahafs@mellanox.com, Honnappa.Nagarahalli@arm.com Date: Wed, 08 May 2019 10:27:56 +0200 Message-ID: <3637602.VAhMH9uBB3@xps> In-Reply-To: <20190508020400.37317-1-yskoh@mellanox.com> References: <20190508020400.37317-1-yskoh@mellanox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] doc: add Mellanox BlueField platform guide X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 May 2019 08:28:00 -0000 08/05/2019 04:04, Yongseok Koh: > --- a/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst > +++ b/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst > +.. _getting_the_prerequisite_library: The name of this anchor should specify "arm". > + > Getting the prerequisite library > -------------------------------- [...] > --- /dev/null > +++ b/doc/guides/platform/bluefield.rst > +Toolchains, OS and drivers can be downloaded and installed individually on the > +Web. But it is recommended to follow instructions at `Mellanox BlueField > +Software Website `_. Please split lines more often to avoid a line break in the middle of the link name. [...] > +Such required libraries can be cross-compiled and installed on to the cross > +toolchain directory like depicted in :ref:`getting_the_prerequisite_library`, > +but those can also be simply copied from the filesystem of a working BlueField > +platform. The following is to create such supplementary tarball on a BlueField > +platform. We are talking about cross-compilation? So we do the following commands on a x86 machine? I think I don't understand, it seems to be on BlueField. Please make it explicit below. > +.. code-block:: console > + > + mkdir -p aarch64-linux-gnu/libc > + pushd $PWD > + cd aarch64-linux-gnu/libc > + > + # Copy libraries > + mkdir -p lib64 > + cp -a /lib64/libibverbs* lib64/ > + cp -a /lib64/libmnl* lib64/ > + cp -a /lib64/libmlx5* lib64/ > + cp -a /lib64/libnl-3* lib64/ > + cp -a /lib64/libnl-route-3* lib64/ > + > + # Copy header files > + mkdir -p usr/include/infiniband > + mkdir -p usr/include/libmnl > + cp -a /usr/include/infiniband/ib_user_ioctl_verbs.h usr/include/infiniband/ > + cp -a /usr/include/infiniband/mlx5*.h usr/include/infiniband/ > + cp -a /usr/include/infiniband/tm_types.h usr/include/infiniband/ > + cp -a /usr/include/infiniband/verbs*.h usr/include/infiniband/ > + cp -a /usr/include/libmnl/libmnl.h usr/include/libmnl/ > + > + # Create supplementary tarball > + popd > + tar cf aarch64-linux-gnu-mlx.tar aarch64-linux-gnu/ > + > +Then, untar the tarball at the cross toolchain directory on the x86 host. > + > +.. code-block:: console > + > + cd $(dirname $(which aarch64-linux-gnu-gcc))/.. > + tar xf aarch64-linux-gnu-mlx.tar OK, this step is clearly on x86. > +- make build Should it be a sub-title instead of a list item? > + > +.. code-block:: console > + > + make config T=arm64-bluefield-linuxapp-gcc > + make -j CROSS=aarch64-linux-gnu- CONFIG_RTE_KNI_KMOD=n CONFIG_RTE_EAL_IGB_UIO=n > + > +- meson build > + > +.. code-block:: console > + > + meson build --cross-file config/arm/arm64_bluefield_linux_gcc > + ninja -C build [...] > --- a/doc/guides/rel_notes/release_19_05.rst > +++ b/doc/guides/rel_notes/release_19_05.rst > +* **Added new platform specific guide:** > + > + * BlueField (Mellanox) I don't think a doc deserves to be in the release notes. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 379B2A0096 for ; Wed, 8 May 2019 10:28:02 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 4829B3772; Wed, 8 May 2019 10:28:01 +0200 (CEST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id BB6F4374C for ; Wed, 8 May 2019 10:27:59 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 320952217D; Wed, 8 May 2019 04:27:59 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 08 May 2019 04:27:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=azhnOVIDkJRGgeS26frChPunKpQGbbBWsci5Lqm4B8k=; b=HEPu1TWrkJ2f boToTiZ8M7x4ppIs0zl7JJYQl0d416DuT4RJyeJpgR182R25gXmdVXjSFsrcCz+r 3MSgRUv0ejEgjbsPWnDfGlOIP15tJ0CJ63YCOnaAVVn8M2maaGfP6RoKD2VaAsAR 8tgneG3dnnrenlXp7Izrxata87mg+Sk= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=azhnOVIDkJRGgeS26frChPunKpQGbbBWsci5Lqm4B 8k=; b=JwR4pL5n0LQdf+myLhs4B3r0ibCvLIqKCA9pTz87lEO9hBc71NHENuHVA DkyOAohy7TCmJmbhr1PTy9DG8QdWGHyTWIkNGzgwz/WUzT4h8TKCUQAU5rvLzXfi R302hykLaUs9SyMhXz+UhmOunsCrJufrrQUhbfmUVvihcW/gvuMp4WPjwL/TTbuu 9afJ9IyErLocSFT7MORbhMk/WL9p0/OkIc5jkakGYOWwQ5SyyRU26VbFrnIgOtzk tKPmEpr03SpCByt0tzgY14jvoM3d/Nv6eMy/JbS2fdN9YFZXeMqTbwmbfnYEXUMP h65YuLCZpvieHqXyWclqCFR25G/8A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrkeefgddtudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucffoh hmrghinhepmhgvlhhlrghnohigrdgtohhmnecukfhppeejjedrudefgedrvddtfedrudek geenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnh gvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id B9409103CA; Wed, 8 May 2019 04:27:57 -0400 (EDT) From: Thomas Monjalon To: Yongseok Koh Cc: dev@dpdk.org, jerinj@marvell.com, shahafs@mellanox.com, Honnappa.Nagarahalli@arm.com Date: Wed, 08 May 2019 10:27:56 +0200 Message-ID: <3637602.VAhMH9uBB3@xps> In-Reply-To: <20190508020400.37317-1-yskoh@mellanox.com> References: <20190508020400.37317-1-yskoh@mellanox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH] doc: add Mellanox BlueField platform guide X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190508082756.ftIRSU5Q96M1szMnaEeUII2cLi1NOjlXda0tcsk0kIc@z> 08/05/2019 04:04, Yongseok Koh: > --- a/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst > +++ b/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst > +.. _getting_the_prerequisite_library: The name of this anchor should specify "arm". > + > Getting the prerequisite library > -------------------------------- [...] > --- /dev/null > +++ b/doc/guides/platform/bluefield.rst > +Toolchains, OS and drivers can be downloaded and installed individually on the > +Web. But it is recommended to follow instructions at `Mellanox BlueField > +Software Website `_. Please split lines more often to avoid a line break in the middle of the link name. [...] > +Such required libraries can be cross-compiled and installed on to the cross > +toolchain directory like depicted in :ref:`getting_the_prerequisite_library`, > +but those can also be simply copied from the filesystem of a working BlueField > +platform. The following is to create such supplementary tarball on a BlueField > +platform. We are talking about cross-compilation? So we do the following commands on a x86 machine? I think I don't understand, it seems to be on BlueField. Please make it explicit below. > +.. code-block:: console > + > + mkdir -p aarch64-linux-gnu/libc > + pushd $PWD > + cd aarch64-linux-gnu/libc > + > + # Copy libraries > + mkdir -p lib64 > + cp -a /lib64/libibverbs* lib64/ > + cp -a /lib64/libmnl* lib64/ > + cp -a /lib64/libmlx5* lib64/ > + cp -a /lib64/libnl-3* lib64/ > + cp -a /lib64/libnl-route-3* lib64/ > + > + # Copy header files > + mkdir -p usr/include/infiniband > + mkdir -p usr/include/libmnl > + cp -a /usr/include/infiniband/ib_user_ioctl_verbs.h usr/include/infiniband/ > + cp -a /usr/include/infiniband/mlx5*.h usr/include/infiniband/ > + cp -a /usr/include/infiniband/tm_types.h usr/include/infiniband/ > + cp -a /usr/include/infiniband/verbs*.h usr/include/infiniband/ > + cp -a /usr/include/libmnl/libmnl.h usr/include/libmnl/ > + > + # Create supplementary tarball > + popd > + tar cf aarch64-linux-gnu-mlx.tar aarch64-linux-gnu/ > + > +Then, untar the tarball at the cross toolchain directory on the x86 host. > + > +.. code-block:: console > + > + cd $(dirname $(which aarch64-linux-gnu-gcc))/.. > + tar xf aarch64-linux-gnu-mlx.tar OK, this step is clearly on x86. > +- make build Should it be a sub-title instead of a list item? > + > +.. code-block:: console > + > + make config T=arm64-bluefield-linuxapp-gcc > + make -j CROSS=aarch64-linux-gnu- CONFIG_RTE_KNI_KMOD=n CONFIG_RTE_EAL_IGB_UIO=n > + > +- meson build > + > +.. code-block:: console > + > + meson build --cross-file config/arm/arm64_bluefield_linux_gcc > + ninja -C build [...] > --- a/doc/guides/rel_notes/release_19_05.rst > +++ b/doc/guides/rel_notes/release_19_05.rst > +* **Added new platform specific guide:** > + > + * BlueField (Mellanox) I don't think a doc deserves to be in the release notes.