From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk0-f195.google.com (mail-qk0-f195.google.com [209.85.220.195]) by dpdk.org (Postfix) with ESMTP id BCE0129CD for ; Wed, 29 Jun 2016 04:39:13 +0200 (CEST) Received: by mail-qk0-f195.google.com with SMTP id j2so7201187qkf.1 for ; Tue, 28 Jun 2016 19:39:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1ieDwk0fhaYkUzuzAUfnjhunh3wUaarlFIXVpfMc7BI=; b=clYw6pX8njZc2Xc033iasq5kLTTkacUKZhpsTLHVCpr8AYjJwfDQwNZUnqHKzjYDhc 5MKCGABXaQzrACVJUxzWOXO54nRvZoeKGI8nVzxviHfk+Otew7gs4YJ3kpGStfY2VkVl mWNrTOZzUxu2OWdY3UJ/pbqeM0jUtH94sun9CSKaJpXZE0ulW8zDiJfburd0KY/KPnGN g2h0U7Xd27y6Q3WLJTOLyo/YZUUA8Xu/M0+WWasdNo1ropu/XTbQxfhKU7HXrDS7wLVh NIaX3gIlFwAC8NskdOH2ieSVLKUw1rE9t1/9px8DWdMwzArSVnmWh7kE2p1Yvv/VbWlA W2eA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1ieDwk0fhaYkUzuzAUfnjhunh3wUaarlFIXVpfMc7BI=; b=E1efRBHodxs5FP6j+CbOteKnsz3HaeSnElenS/T+6OpTodhZs7gyQOaOzqE/PY7i5L AHqOiVOHQIcNzehWTh3rNQ5ZnDB/fqHvDih4lP8CJQq2Gj287sY5cIapPWDHFEb9EA8P L7VXodLkuwLJDxGGPXVEDWPGm3n2gjyVjkscGw4KYWUBS6ZfddYhOj79vNAs+cmIDXpA cXLjdKL29fQFMhztHIf4Fs0CtMHwUOzvrOAeBEmYeegsIB2Hb60ctf+yj5c67NFm+wIV /F64I4KWog0SS02RRRpfI9qd6/94KCe4iKoVnPvX83K/dZMitw/XBVNk4QE4Nk5tlpVE 2fOQ== X-Gm-Message-State: ALyK8tK24Hety9uyKCWIM6QhXQDfVDsDDoIBM0NOO/SQ4mHFUL/Lvb2q/XhnnvPplFAVygCddC9qlfb2HYkaxA== X-Received: by 10.129.153.8 with SMTP id q8mr2177422ywg.227.1467167953166; Tue, 28 Jun 2016 19:39:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.13.130 with HTTP; Tue, 28 Jun 2016 19:38:43 -0700 (PDT) In-Reply-To: <5762C645.4000509@intel.com> References: <57515FB0.3040800@intel.com> <9B0331B6EBBD0E4684FBFAEDA55776F92CD5CBC7@HASMSX110.ger.corp.intel.com> <5762C645.4000509@intel.com> From: =?UTF-8?B?TWFydGlueCAtIOOCuOOCp+ODvOODoOOCug==?= Date: Tue, 28 Jun 2016 22:38:43 -0400 Message-ID: To: Ferruh Yigit Cc: "Rosen, Rami" , dev Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] Can't build DPDK-16.04 on CentOS 6.8 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 02:39:14 -0000 On 16 June 2016 at 11:31, Ferruh Yigit wrote: > On 6/15/2016 7:59 PM, Martinx - =E3=82=B8=E3=82=A7=E3=83=BC=E3=83=A0=E3= =82=BA wrote: > > On 13 June 2016 at 12:15, Martinx - =E3=82=B8=E3=82=A7=E3=83=BC=E3=83= =A0=E3=82=BA > > > wrote: > > > > > > > > On 12 June 2016 at 11:30, Rosen, Rami > > wrote: > > > > Hi Thiago, > > > > > Any clue? > > > > Sure. This is the reason: in > > dpdk-16.04/lib/librte_eal/linuxapp/igb_uio we have: > > .... > > #ifndef PCI_MSIX_ENTRY_SIZE > > #define PCI_MSIX_ENTRY_SIZE 16 > > #define PCI_MSIX_ENTRY_LOWER_ADDR 0 > > #define PCI_MSIX_ENTRY_UPPER_ADDR 4 > > #define PCI_MSIX_ENTRY_DATA 8 > > #define PCI_MSIX_ENTRY_VECTOR_CTRL 12 > > #define PCI_MSIX_ENTRY_CTRL_MASKBIT 1 > > #endif > > ... > > > > The root cause of the problem is due to that in CentOS 6.8, > > PCI_MSIX_ENTRY_SIZE is defined; this > > causes *avoiding* having the PCI_MSIX_ENTRY_CTRL_MASKBIT > > definition as shown above. > > > > The definition of PCI_MSIX_ENTRY_SIZE is due to the following > > patch, which was introduced in CentOS 6.8, which moved > > PCI_MSIX_ENTRY_SIZE from the inner drivers/pci/msi.h header fil= e > > into include/linux/pci_regs.h, > > The linux/pci_regs.h is included in the pci.h header, which is > > used by the igb_uio.c, which failed in compilation. > > > > "PATCH 1/8] PCI: MSI: Move MSI-X entry definition to pci_regs.h= " > > > > --- a/drivers/pci/msi.h > > +++ b/drivers/pci/msi.h > > @@ -6,12 +6,6 @@ > > #ifndef MSI_H > > #define MSI_H > > > > -#define PCI_MSIX_ENTRY_SIZE 16 > > ... > > ... > > ... > > diff --git a/include/linux/pci_regs.h b/include/linux/pci_regs.= h > > index 455b9cc..acfc224 100644 > > --- a/include/linux/pci_regs.h > > +++ b/include/linux/pci_regs.h > > @@ -307,6 +307,13 @@ > > #define PCI_MSIX_FLAGS_MASKALL (1 << 14) > > #define PCI_MSIX_FLAGS_BIRMASK (7 << 0) > > > > +/* MSI-X entry's format */ > > +#define PCI_MSIX_ENTRY_SIZE 16 > > .... > > > > > http://linux-pci.vger.kernel.narkive.com/cZquopIw/patch-1-8-pci-msi-move-= msi-x-entry-definition-to-pci-regs-h > > > > See also: > > rpm -qp --changelog kernel-devel-2.6.32-642.el6.x86_64.rpm | > > grep "Move MSI-X entry" > > warning: kernel-devel-2.6.32-642.el6.x86_64.rpm: Header V3 > > RSA/SHA1 Signature, key ID c105b9de: NOKEY > > - [pci] msi: Move MSI-X entry definition to pci_regs.h (Myron > > Stowe) [1288629 > > > > > > A proper patch which checks kernel version can fix it. > > > > Regards, > > Rami Rosen > > Intel Corporation > > > > > > Interesting! > > > > Do you have this proper fix? I would like to build and use DPDK on > > CentOS 6.8... > > > > Thank you for your reply! > > > > Best, > > Thiago > > > > > > Hey guys, > > > > I tried something different, just for testing, and it also doesn't buil= d. > > > > What I tried was to install the "centos-release-xen" repo, and run "yum > > upgrade" in my CentOS 6.8 box, this way, I can receive a new Kernel for > > it, which is "3.18.34-20.el6.x86_64", and here is the DPDK build error > now: > > > > --- > > ........... > > CC eal_common_dev.o > > cc1: warnings being treated as errors > > > /root/rpmbuild/BUILD/dpdk-16.04/x86_64-default-linuxapp-gcc/build/lib/lib= rte_eal/linuxapp/igb_uio/igb_uio.c: > > In function 'igbuio_pci_probe': > > /usr/src/kernels/3.18.34-20.el6.x86_64/include/linux/slab.h:582: error: > > inlining failed in call to 'kzalloc.clone.0': --param > > max-inline-insns-single limit reached > > > /root/rpmbuild/BUILD/dpdk-16.04/x86_64-default-linuxapp-gcc/build/lib/lib= rte_eal/linuxapp/igb_uio/igb_uio.c:383: > > error: called from here > > make[8]: *** > > > [/root/rpmbuild/BUILD/dpdk-16.04/x86_64-default-linuxapp-gcc/build/lib/li= brte_eal/linuxapp/igb_uio/igb_uio.o] > > Error 1 > > make[7]: *** > > > [_module_/root/rpmbuild/BUILD/dpdk-16.04/x86_64-default-linuxapp-gcc/buil= d/lib/librte_eal/linuxapp/igb_uio] > > Error 2 > <...> > > I did able to compile dpdk16.04 with 3.18.34-20.el6.x86_64, is the > problem can be related to gcc version? For me both gcc 5.3.1 and 4.9.3 > worked fine. > > Or for "max-inline-insns-single limit reached" issue you can try > increasing the gcc limit: -finline-limit=3Dn > > Hey Ferruh, I'm facing this "max-inline-insns-single limit reached" problem now (while trying to compile DPDK-16.04 on "3.18.34-20.el6.x86_64". So, as you suggested, I changed the limit from 100 to 400, here: dpdk-16.04/lib/librte_eal/linuxapp/igb_uio/Makefile ...and it worked! The CentOS 6.8 "centos-xen-release" YUM/RPM package brings Linux 3.18 to it, a new life for an old O.S... That's good... :-) Thanks! Thiago > I'm still looking for a way to build and package the latest DPDK on > > CentOS 6.8 box. > > > > I appreciate any help... > > > > Thanks! > > Thiago > >