From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id C3733235 for ; Thu, 21 Feb 2019 17:02:49 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Feb 2019 08:02:48 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.58,395,1544515200"; d="scan'208";a="145406222" Received: from irsmsx151.ger.corp.intel.com ([163.33.192.59]) by fmsmga002.fm.intel.com with ESMTP; 21 Feb 2019 08:02:47 -0800 Received: from irsmsx111.ger.corp.intel.com (10.108.20.4) by IRSMSX151.ger.corp.intel.com (163.33.192.59) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 21 Feb 2019 16:02:47 +0000 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.219]) by irsmsx111.ger.corp.intel.com ([169.254.2.149]) with mapi id 14.03.0415.000; Thu, 21 Feb 2019 16:02:47 +0000 From: "Van Haaren, Harry" To: Alex Kiselev , "users@dpdk.org" Thread-Topic: [dpdk-users] build dpdk for a cpu that doesn't support avx Thread-Index: AQHUyfRnh8H39i7720e8di+Ey9FnH6XqYYQAgAAGyFA= Date: Thu, 21 Feb 2019 16:02:46 +0000 Message-ID: References: <1681745409.20190221174703@therouter.net> <872839432.20190221183254@therouter.net> In-Reply-To: <872839432.20190221183254@therouter.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMzRiOTZmZWMtODkwOS00OGFjLTkwZjktOGMwNWNhYzViOTU5IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiNEhzdkRVZGZxR09BWFwvK2x2RjMyMkxqWW1WM1FLWHM3WGVNMFBSa2xoU1NFYlNsN1RGZm1IdWlPZStYN2tVY00ifQ== x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] build dpdk for a cpu that doesn't support avx X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Feb 2019 16:02:50 -0000 > -----Original Message----- > From: users [mailto:users-bounces@dpdk.org] On Behalf Of Alex Kiselev > Sent: Thursday, February 21, 2019 3:33 PM > To: users@dpdk.org > Subject: Re: [dpdk-users] build dpdk for a cpu that doesn't support avx >=20 > It looks like I've found a way: >=20 > I edited $RTE_SDK/config/defconfig_x86_64-native-linuxapp-gcc > CONFIG_RTE_MACHINE=3D"x86-64" >=20 > and then I used > make EXTRA_CFLAGS=3D"-march=3Dx86-64 -mpopcnt -mmmx -msse -msse2 -msse3= -mssse3 > -msse4.1 -msse4.2 -mfpmath=3Dsse -mpopcnt" >=20 > The application has started successfully. > But I am wondering, maybe I've missed something and there are potential b= ugs > in this way? >=20 > > Hi. >=20 > > Is it possible to build DPDK application on a machine that do have AVX > support > > for use at another machine that doesn't have AVX feature? >=20 > > Thanks. Using -march to manually tune should work fine, just be aware of mistakes m= ade; this is an error prone method.. As per the GCC docs, you can target specific CPU families, and the optimal = flags will be selected: https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html Example: -march=3Dgoldmont-plus With make, EXTRA_CFLAGS=3D"-march=3DNAME-HERE" should work With Meson, cd && meson configure -Dc_args=3D"-march=3DNAME-HER= E" I guess there's a prettier method for meson, but the above works here :) Hope that helps, -Harry