From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 77280A04A5; Thu, 18 Jun 2020 04:02:45 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id D9FE425B3; Thu, 18 Jun 2020 04:02:44 +0200 (CEST) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id C31741150 for ; Thu, 18 Jun 2020 04:02:42 +0200 (CEST) IronPort-SDR: eHqDuzkCklmcPaIyzDK4PjuLq3uEwOM0OLnIY1EqD0bL3doplhl1Uk8Q8EF06HRNfWM8YeGH00 /A2gNhokGs9g== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Jun 2020 19:02:41 -0700 IronPort-SDR: H0FDphc129Dh7xSYuFgLsLHLymq4wEnaatk5PGC5NqLcdySf1aYBVfp2lwSm7JkooK7vWfoFLZ 54+Ro6Y/zbkg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.73,524,1583222400"; d="scan'208";a="383385123" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by fmsmga001.fm.intel.com with ESMTP; 17 Jun 2020 19:02:41 -0700 Received: from fmsmsx610.amr.corp.intel.com (10.18.126.90) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.439.0; Wed, 17 Jun 2020 19:02:41 -0700 Received: from fmsmsx607.amr.corp.intel.com (10.18.126.87) by fmsmsx610.amr.corp.intel.com (10.18.126.90) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Wed, 17 Jun 2020 19:02:40 -0700 Received: from FMSEDG001.ED.cps.intel.com (10.1.192.133) by fmsmsx607.amr.corp.intel.com (10.18.126.87) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.1713.5 via Frontend Transport; Wed, 17 Jun 2020 19:02:40 -0700 Received: from NAM10-DM6-obe.outbound.protection.outlook.com (104.47.58.103) by edgegateway.intel.com (192.55.55.68) with Microsoft SMTP Server (TLS) id 14.3.439.0; Wed, 17 Jun 2020 19:02:40 -0700 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=k1BMbqCk+R3OtBx3YUtF5bzrrmT3fu7a+G/f8bLF/M39tqc8zwh+toSZ+lK/pVoi4POC5vjwyEczkYvoMJFwqI4mXMWOq8vahcVpuVg/Jldol0Qsgx7GCgiAveSGxOCMAcCEmYQOOSLPzPQ1nl1S3MnufbgLtFR7XBdUjKX8UlcU2oIBQ6aI4qihlhVB+6gRZC6mw0j707ZmRhPzR0gE4jzzq/eByGrkBVbl8GGh5kxqZCopeYMdBTpJy5otjiGLrOIy5XbwyhjTR1KEzwLhl8e/W4I3GOmdFaChkX7rCIvy1mQBUvlKuWXFkE6NzDEszgl8exrPnoVlHMKNmYEBeg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4W9VZYOCk91YzBrn/nMxvoBgk+Xw1ZHiI7tLTArrjJQ=; b=g7mHm4PEg8J1ppmTboXBtIi67QGTWPZEI5L90ir126HhBV35GEaCRdGUEB1SuDVlVRDh1z9IXL+6WKjZRDmj/WtiBfJ0n1kNFSlvFvnEViqMzs1HuseC7RfqVX8nZcNWxeeWEXqzYim/D6cEzZCYIZ30rSoRnZcRsrtIBnDp2YPGj1feOUc20AGX8HsN+Vp0Av3HNsGhGh7bFkiQC7iJYN5e1eL/DwfaVzE+u+sOLGPQfTbQHQ8gpgSYjaUlbRfi6SY7UENL4BA8IwQ9u2nEP6coVm3ifZhm0IQKiho2XAfonJN8yPYi09LYX88BXEc282ww1LiQWcYyEtykK/R/tA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=intel.com; dmarc=pass action=none header.from=intel.com; dkim=pass header.d=intel.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel.onmicrosoft.com; s=selector2-intel-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4W9VZYOCk91YzBrn/nMxvoBgk+Xw1ZHiI7tLTArrjJQ=; b=S0iIfPRzq0RrTwD3sjqpPl1AKwp8XClKRNjI7DL42Mk2VWUDahW2rp/GL/EEHU8Yt/7tGbMSi4Ch/KfdUD81br+6F3+FomDckK/ts/VQEmgRCBfCn0jBnRAL7HqUodLwVAPY24Z58B7RGLnNSeu6mzRJfz9BSXuXsDYa3At0LSE= Received: from BY5PR11MB4451.namprd11.prod.outlook.com (2603:10b6:a03:1cb::30) by BYAPR11MB3365.namprd11.prod.outlook.com (2603:10b6:a03:7e::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3088.24; Thu, 18 Jun 2020 02:02:38 +0000 Received: from BY5PR11MB4451.namprd11.prod.outlook.com ([fe80::e4c9:8ec0:1923:1150]) by BY5PR11MB4451.namprd11.prod.outlook.com ([fe80::e4c9:8ec0:1923:1150%3]) with mapi id 15.20.3109.021; Thu, 18 Jun 2020 02:02:38 +0000 From: "Chautru, Nicolas" To: Thomas Monjalon , "dev@dpdk.org" CC: "david.marchand@redhat.com" , "Richardson, Bruce" , "Mcnamara, John" , "Kovacevic, Marko" , Jay Zhou , Ajit Khaparde , Somnath Kotur , "Lu, Wenzhuo" , "Xing, Beilei" , "Iremonger, Bernard" Thread-Topic: [PATCH 2/4] doc: remove build instructions where unneeded Thread-Index: AQHWRQlnQnZTD54bOkCmi0xKVz11kKjdnPmg Date: Thu, 18 Jun 2020 02:02:38 +0000 Message-ID: References: <20200618004218.3730743-1-thomas@monjalon.net> <20200618004218.3730743-3-thomas@monjalon.net> In-Reply-To: <20200618004218.3730743-3-thomas@monjalon.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-reaction: no-action dlp-version: 11.2.0.6 authentication-results: monjalon.net; dkim=none (message not signed) header.d=none;monjalon.net; dmarc=none action=none header.from=intel.com; x-originating-ip: [45.28.143.88] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 635a6c12-8998-40e4-815a-08d8132bad3c x-ms-traffictypediagnostic: BYAPR11MB3365: x-ld-processed: 46c98d88-e344-4ed4-8496-4ed7712e255d,ExtAddr x-ms-exchange-transport-forked: True x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:989; x-forefront-prvs: 0438F90F17 x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: mNRHnFKm9n+nwDUri07XndB5hzULdHT5/bxPzSTkhaMllpeiBa5jaTteUGTosAz72u8K8EQ4kWLcCD1aUZXkYta3HEAzin34GT/auvwDytW8yfr+CjAlyGNpWvBK8wIIzhILsGmuiIQcSF7ps9tm/cbkVpT96h+Y6CCuQ/7w3eX7SvANp916hhCTRLhpcL/2IMJhw1j3B7VgjS/iz4GwqYWnE2KUHrSm+QmtrTHaiD7Ib4DwlwymugvMXRSgXWI2sr9hof6UU5NJQrt+Fvtem1orbRByS3NHqYfrJdT27f1nDa+Ss4bvGN8BzPZ7FkgW x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BY5PR11MB4451.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(396003)(376002)(346002)(39860400002)(366004)(136003)(8676002)(4326008)(26005)(83380400001)(33656002)(316002)(55016002)(2906002)(9686003)(478600001)(7696005)(110136005)(8936002)(54906003)(66556008)(186003)(76116006)(86362001)(6506007)(66446008)(71200400001)(66476007)(64756008)(5660300002)(52536014)(107886003)(66946007); DIR:OUT; SFP:1102; x-ms-exchange-antispam-messagedata: t6VX4PkDoWpIkn+qLnxREtu9WXsPfmzl/vk/HlyKtIUPtza26E53Uz+k3FIWifLH3T7yxCwF500YaWxnzml8IHcZXh9iB6hWTQRYwGxgXPzA61rRKl8xxzPtZzt7DV/Wyjrb+d2TeUtzYQGysnQriC9cjH9mqf2ujBZrluqEmYV6NWrdhhdmrUo90C3BRxshTvh7/Os/P8WT8RVt+WVgFAzR7bde3GMYXOHQp8+ovThmswSH8tQf2VFlaxj3hHl/dYKzJnjn9CPZKzHYxlxh0ZvOR03+DkJkx/TWJ3zlc11Rf3yzbksBn2E8Od8yY6KmTms8sEpyq1/xxb9ftMujN3Dy7aBRv1w0wUldV7MVbwxiWGr32KHwSEK+cTMFGPVkrBaa6JixrvrxeFqTeBiCXAsxSBk3zmzbhhNG4AR+sxfH0DONmJ8Xo6LeC6/7qadL3minFmH5uTS1FVNOC5jC0XEO8+T4xDA0n3p+pKfV8W8= Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: 635a6c12-8998-40e4-815a-08d8132bad3c X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Jun 2020 02:02:38.2621 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 46c98d88-e344-4ed4-8496-4ed7712e255d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: HS12cjHZJfV4wGK0sSLKet6YX5jK2qLvt4FIiPTvrSlVVpLLQdXC25M6dVT4GxcKJ9mpYbYMRlbCn16Lze3ei6bHdJ5yvkeHHWJmoYAwwao= X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3365 X-OriginatorOrg: intel.com Subject: Re: [dpdk-dev] [PATCH 2/4] doc: remove build instructions where unneeded 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" From: Thomas Monjalon > The build should be described only in few places, in order to maintain up= -to- > date, accurate and detailed instructions. > This change is removing some of the unneeded repetitions. >=20 > Signed-off-by: Thomas Monjalon > --- > doc/guides/bbdevs/fpga_5gnr_fec.rst | 7 +-- > doc/guides/bbdevs/fpga_lte_fec.rst | 7 +-- Ok in principle to remove from these BBDEV drivers doc.=20 Should we include link to actual new build steps instead to help with trans= ition? <../prog_guide/build-sdk-meson> Also I see a typo in same paragraph "instuctions" instead of "instructions"= in case you can fix in same commit.=20 > doc/guides/cryptodevs/virtio.rst | 9 +--- > .../virtio_user_for_container_networking.rst | 6 --- > .../linux_gsg/nic_perf_intel_platform.rst | 8 +--- > doc/guides/nics/bnxt.rst | 30 +++---------- > doc/guides/nics/build_and_test.rst | 43 +++---------------- > doc/guides/testpmd_app_ug/build_app.rst | 26 ----------- > 8 files changed, 15 insertions(+), 121 deletions(-) >=20 > diff --git a/doc/guides/bbdevs/fpga_5gnr_fec.rst > b/doc/guides/bbdevs/fpga_5gnr_fec.rst > index 19bba3661f..d5dcd3d765 100644 > --- a/doc/guides/bbdevs/fpga_5gnr_fec.rst > +++ b/doc/guides/bbdevs/fpga_5gnr_fec.rst > @@ -54,12 +54,7 @@ Installation > Section 3 of the DPDK manual provides instuctions on installing and > compiling DPDK. The default set of bbdev compile flags may be found in > config/common_base, where for example the flag to build the FPGA 5GNR > FEC device, ``CONFIG_RTE_LIBRTE_PMD_BBDEV_FPGA_5GNR_FEC``, > -is already set. It is assumed DPDK has been compiled using for instance: > - > -.. code-block:: console > - > - make install T=3Dx86_64-native-linuxapp-gcc > - > +is already set. >=20 > DPDK requires hugepages to be configured as detailed in section 2 of the > DPDK manual. > The bbdev test application has been tested with a configuration 40 x 1GB > hugepages. The diff --git a/doc/guides/bbdevs/fpga_lte_fec.rst > b/doc/guides/bbdevs/fpga_lte_fec.rst > index 206b6f4f9b..191e89fcef 100644 > --- a/doc/guides/bbdevs/fpga_lte_fec.rst > +++ b/doc/guides/bbdevs/fpga_lte_fec.rst > @@ -53,12 +53,7 @@ Installation > Section 3 of the DPDK manual provides instuctions on installing and > compiling DPDK. The default set of bbdev compile flags may be found in > config/common_base, where for example the flag to build the FPGA LTE FEC > device, ``CONFIG_RTE_LIBRTE_PMD_BBDEV_FPGA_LTE_FEC``, is already -set. It > is assumed DPDK has been compiled using for instance: > - > -.. code-block:: console > - > - make install T=3Dx86_64-native-linuxapp-gcc > - > +set. >=20 > DPDK requires hugepages to be configured as detailed in section 2 of the > DPDK manual. > The bbdev test application has been tested with a configuration 40 x 1GB > hugepages. The diff --git a/doc/guides/cryptodevs/virtio.rst > b/doc/guides/cryptodevs/virtio.rst > index 1496ec9208..2c46bda866 100644 > --- a/doc/guides/cryptodevs/virtio.rst > +++ b/doc/guides/cryptodevs/virtio.rst > @@ -73,14 +73,7 @@ number of the virtio-crypto device: > echo -n 0000:00:04.0 > /sys/bus/pci/drivers/virtio-pci/unbind > echo "1af4 1054" > /sys/bus/pci/drivers/uio_pci_generic/new_id >=20 > -Finally the front-end virtio crypto PMD driver can be installed: > - > -.. code-block:: console > - > - cd to the top-level DPDK directory > - sed -i 's,\(CONFIG_RTE_LIBRTE_PMD_VIRTIO_CRYPTO\)=3Dn,\1=3Dy,' > config/common_base > - make config T=3Dx86_64-native-linux-gcc > - make install T=3Dx86_64-native-linux-gcc > +Finally the front-end virtio crypto PMD driver can be installed. >=20 > Tests > ----- > diff --git a/doc/guides/howto/virtio_user_for_container_networking.rst > b/doc/guides/howto/virtio_user_for_container_networking.rst > index f31d918bcd..412b29664b 100644 > --- a/doc/guides/howto/virtio_user_for_container_networking.rst > +++ b/doc/guides/howto/virtio_user_for_container_networking.rst > @@ -56,12 +56,6 @@ Sample Usage > Here we use Docker as container engine. It also applies to LXC, Rocket w= ith > some minor changes. >=20 > -#. Compile DPDK. > - > - .. code-block:: console > - > - make install RTE_SDK=3D`pwd` T=3Dx86_64-native-linux-gcc > - > #. Write a Dockerfile like below. >=20 > .. code-block:: console > diff --git a/doc/guides/linux_gsg/nic_perf_intel_platform.rst > b/doc/guides/linux_gsg/nic_perf_intel_platform.rst > index 1dabbce244..08be5d58b9 100644 > --- a/doc/guides/linux_gsg/nic_perf_intel_platform.rst > +++ b/doc/guides/linux_gsg/nic_perf_intel_platform.rst > @@ -124,17 +124,11 @@ The following are some recommendations on GRUB > boot settings: > Configurations before running DPDK > ---------------------------------- >=20 > -1. Build the DPDK target and reserve huge pages. > +1. Reserve huge pages. > See the earlier section on :ref:`linux_gsg_hugepages` for more detail= s. >=20 > - The following shell commands may help with building and configuration= : > - > .. code-block:: console >=20 > - # Build DPDK target. > - cd dpdk_folder > - make install T=3Dx86_64-native-linux-gcc -j > - > # Get the hugepage size. > awk '/Hugepagesize/ {print $2}' /proc/meminfo >=20 > diff --git a/doc/guides/nics/bnxt.rst b/doc/guides/nics/bnxt.rst index > ed650187e0..a53cdad21d 100644 > --- a/doc/guides/nics/bnxt.rst > +++ b/doc/guides/nics/bnxt.rst > @@ -56,33 +56,15 @@ The BNXT PMD supports operating with: > * Linux igb_uio > * BSD nic_uio >=20 > -Compiling BNXT PMD > ------------------- > - > -To compile the BNXT PMD: > - > -.. code-block:: console > - > - make config T=3Dx86_64-native-linux-gcc && make // for x86-64 > - make config T=3Dx86_32-native-linux-gcc && make // for x86-32 > - make config T=3Darmv8a-linux-gcc && make // for ARMv8 > - > -Bind the device to one of the kernel modules listed above > - > -.. code-block:: console > - > - ./dpdk-devbind.py -b vfio-pci|igb_uio|uio_pci_generic > bus_id:device_id.function_id > - > -Load an application (e.g. testpmd) with a default configuration (e.g. a = single - > TX /RX queue): > - > -.. code-block:: console > - > - ./testpmd -c 0xF -n 4 -- -i --portmask=3D0x1 --nb-cores=3D2 > - > Running BNXT PMD > ---------------- >=20 > +Bind the device to one of the kernel modules listed above > + > +.. code-block:: console > + > + ./dpdk-devbind.py -b vfio-pci|igb_uio|uio_pci_generic > + bus_id:device_id.function_id > + > The BNXT PMD can run on PF or VF. >=20 > PCI-SIG Single Root I/O Virtualization (SR-IOV) involves the direct assi= gnment > diff --git a/doc/guides/nics/build_and_test.rst > b/doc/guides/nics/build_and_test.rst > index f99e019ff3..3138c0f880 100644 > --- a/doc/guides/nics/build_and_test.rst > +++ b/doc/guides/nics/build_and_test.rst > @@ -19,45 +19,12 @@ information on how to build and run testpmd. > Driver Compilation > ------------------ >=20 > -To compile a PMD for a platform, run make with appropriate target as sho= wn > below. > -Use "make" command in Linux and "gmake" in FreeBSD. This will also build > testpmd. > +To compile a PMD for a platform, build DPDK as described in the > +"Getting Started Guide" for your platform. > +This will also build testpmd. >=20 > -To check available targets: > - > -.. code-block:: console > - > - cd > - make showconfigs > - > -Example output: > - > -.. code-block:: console > - > - arm-armv7a-linux-gcc > - arm64-armv8a-linux-gcc > - arm64-dpaa-linux-gcc > - arm64-thunderx-linux-gcc > - arm64-xgene1-linux-gcc > - i686-native-linux-gcc > - i686-native-linux-icc > - ppc_64-power8-linux-gcc > - x86_64-native-freebsd-clang > - x86_64-native-freebsd-gcc > - x86_64-native-linux-clang > - x86_64-native-linux-gcc > - x86_64-native-linux-icc > - x86_x32-native-linux-gcc > - > -To compile a PMD for Linux x86_64 gcc target, run the following "make" > command: > - > -.. code-block:: console > - > - make install T=3Dx86_64-native-linux-gcc > - > -Use ARM (ThunderX, DPAA, X-Gene) or PowerPC target for respective > platform. > - > -For more information, refer to the :ref:`Getting Started Guide for Linux > ` -or :ref:`Getting Started Guide for FreeBSD ` > depending on your platform. > +Detailed instructions are available > +in the :doc:`meson build guide <../prog_guide/build-sdk-meson>`. >=20 > Running testpmd in Linux > ------------------------ > diff --git a/doc/guides/testpmd_app_ug/build_app.rst > b/doc/guides/testpmd_app_ug/build_app.rst > index d1ca9f3d19..4d08db75b5 100644 > --- a/doc/guides/testpmd_app_ug/build_app.rst > +++ b/doc/guides/testpmd_app_ug/build_app.rst > @@ -6,29 +6,3 @@ Compiling the Application >=20 > The ``testpmd`` application is compiled as part of the main compilation = of > the DPDK libraries and tools. > Refer to the DPDK Getting Started Guides for details. > -The basic compilation steps are: > - > -#. Set the required environmental variables and go to the source direct= ory: > - > - .. code-block:: console > - > - export RTE_SDK=3D/path/to/rte_sdk > - cd $RTE_SDK > - > -#. Set the compilation target. For example: > - > - .. code-block:: console > - > - export RTE_TARGET=3Dx86_64-native-linux-gcc > - > -#. Build the application: > - > - .. code-block:: console > - > - make install T=3D$RTE_TARGET > - > - The compiled application will be located at: > - > - .. code-block:: console > - > - $RTE_SDK/$RTE_TARGET/app/testpmd > -- > 2.26.2