From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-f67.google.com (mail-wr1-f67.google.com [209.85.221.67]) by dpdk.org (Postfix) with ESMTP id 993E61B443 for ; Wed, 3 Apr 2019 16:51:48 +0200 (CEST) Received: by mail-wr1-f67.google.com with SMTP id t17so8737182wrw.13 for ; Wed, 03 Apr 2019 07:51:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:content-transfer-encoding:user-agent:mime-version; bh=MceFueBMs3TKj+B00P4iqTY1g/XK3tX2SUqfT73Q3hs=; b=aMZWIFQzn/Ma1HcAWmkTdSen/J8Cc8EGAj/toqKcz91x1/ln8i8Jc+ikvXNiNrk5LG Lt8ZNLTrzWxHVE5jGtJjUqxc0othDsJquG0RCwyMniZuIWT0XJpsAzb2sMztiIXgd0uz 0qMyGz0JCX3uw8m9Q7EAyzjxbvfx8hcgKUTt90BOC4RSJS9sDQFKLYZSsBGq6oxEpg8Y F7KBbiTBi3Nifkpf1eHVpk+fMftZ3zzXoUvbaa6lbshYOoPaEUYlpRGrkiUdW2HIX4OD myUZUON9UfzLiYEX5ifrTzrLFOGDA4mY9736CQ+Qw9ht+Dg5l669sGyxCR69zjXZ/ZR9 wgBw== X-Gm-Message-State: APjAAAV22Oyy86DZuisnPtdnXA9b6WLGvlOqbAuXleXtQtgOTsyAJpoh 4LdLsD2r20PpML/4gmRVDk4= X-Google-Smtp-Source: APXvYqznztmZd3UWERyNJX+Nbl/kODHkgrXXD3/pFG/esNEMx2C2tFO9DpQVp6lRjCh3qV3wZ4EfVg== X-Received: by 2002:a5d:4843:: with SMTP id n3mr246098wrs.256.1554303108150; Wed, 03 Apr 2019 07:51:48 -0700 (PDT) Received: from localhost ([2a01:4b00:f419:6f00:250:b6ff:feb7:bd60]) by smtp.gmail.com with ESMTPSA id u17sm14067536wmj.1.2019.04.03.07.51.46 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 03 Apr 2019 07:51:46 -0700 (PDT) Message-ID: <8f1ac08396f0deaca458201370c08b1334ee6b84.camel@debian.org> From: Luca Boccassi To: Ye Xiaolong Cc: Ferruh Yigit , dev@dpdk.org Date: Wed, 03 Apr 2019 15:51:46 +0100 In-Reply-To: <20190403144327.GB36385@intel.com> References: <20190402154653.711-1-xiaolong.ye@intel.com> <20190402154653.711-2-xiaolong.ye@intel.com> <20190403095939.GA32340@intel.com> <56ce5855b02d47a085a8d36451561c400f0b039c.camel@debian.org> <0dde8c20e9992047f29d39ad45dcf511244a5297.camel@debian.org> <80c81c0c-cf64-59f8-a592-26cd865fbd89@intel.com> <37073834d0b9a9f5a6e9f39bac3adc5eb29779ab.camel@debian.org> <5bc49c51-04f4-6f73-889d-d3c0ff749784@intel.com> <46d92b70a40581462f5ee3ba301c793c4cf0c2df.camel@debian.org> <20190403144327.GB36385@intel.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.30.5-1 MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v9 1/1] net/af_xdp: introduce AF XDP PMD driver 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, 03 Apr 2019 14:51:48 -0000 On Wed, 2019-04-03 at 22:43 +0800, Ye Xiaolong wrote: > On 04/03, Luca Boccassi wrote: > [snip] > > > Got it. > > >=20 > > > In above steps, 'libbpf' also build from kernel source tree, will > > > it > > > be problem > > > in you builds to not have it build from source? > > >=20 > > > If not, taking into account that xsk.h also will be fixed, only > > > 'tools/include/asm/barrier.h' remains the problem, and it looks > > > like > > > it can be > > > solved, please check above. > >=20 > > libbpf is already packaged separately in Debian and I think other > > distros will follow soon, so it's all good for me once the barrier > > issue is solved. > >=20 > > https://packages.debian.org/buster/libbpf-dev > >=20 > >=20 > > From the makefile's perspective it should not matter where it comes > > from - the headers should be expected to be in /usr/include and the > > library in /usr/lib* - and pkg-config can help with that if > > available. > > And if a user wants to use a custom path, then it's no different > > than > > any of the other dependencies on other external libraries >=20 > From tools/lib/bpf/Makefile, after make install_lib and make > install_headers, > the headers and library would be put in /usr/local/include/bpf and > /usr/local/lib*, > Is it ok? Yes certainly that's fine, that's expected for local installations, and users can specify a prefix with the upstream's makefile if they want to install somewhere else. --=20 Kind regards, Luca Boccassi 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 481CCA0679 for ; Wed, 3 Apr 2019 16:51:51 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 25EC41B447; Wed, 3 Apr 2019 16:51:50 +0200 (CEST) Received: from mail-wr1-f67.google.com (mail-wr1-f67.google.com [209.85.221.67]) by dpdk.org (Postfix) with ESMTP id 993E61B443 for ; Wed, 3 Apr 2019 16:51:48 +0200 (CEST) Received: by mail-wr1-f67.google.com with SMTP id t17so8737182wrw.13 for ; Wed, 03 Apr 2019 07:51:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:content-transfer-encoding:user-agent:mime-version; bh=MceFueBMs3TKj+B00P4iqTY1g/XK3tX2SUqfT73Q3hs=; b=aMZWIFQzn/Ma1HcAWmkTdSen/J8Cc8EGAj/toqKcz91x1/ln8i8Jc+ikvXNiNrk5LG Lt8ZNLTrzWxHVE5jGtJjUqxc0othDsJquG0RCwyMniZuIWT0XJpsAzb2sMztiIXgd0uz 0qMyGz0JCX3uw8m9Q7EAyzjxbvfx8hcgKUTt90BOC4RSJS9sDQFKLYZSsBGq6oxEpg8Y F7KBbiTBi3Nifkpf1eHVpk+fMftZ3zzXoUvbaa6lbshYOoPaEUYlpRGrkiUdW2HIX4OD myUZUON9UfzLiYEX5ifrTzrLFOGDA4mY9736CQ+Qw9ht+Dg5l669sGyxCR69zjXZ/ZR9 wgBw== X-Gm-Message-State: APjAAAV22Oyy86DZuisnPtdnXA9b6WLGvlOqbAuXleXtQtgOTsyAJpoh 4LdLsD2r20PpML/4gmRVDk4= X-Google-Smtp-Source: APXvYqznztmZd3UWERyNJX+Nbl/kODHkgrXXD3/pFG/esNEMx2C2tFO9DpQVp6lRjCh3qV3wZ4EfVg== X-Received: by 2002:a5d:4843:: with SMTP id n3mr246098wrs.256.1554303108150; Wed, 03 Apr 2019 07:51:48 -0700 (PDT) Received: from localhost ([2a01:4b00:f419:6f00:250:b6ff:feb7:bd60]) by smtp.gmail.com with ESMTPSA id u17sm14067536wmj.1.2019.04.03.07.51.46 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 03 Apr 2019 07:51:46 -0700 (PDT) Message-ID: <8f1ac08396f0deaca458201370c08b1334ee6b84.camel@debian.org> From: Luca Boccassi To: Ye Xiaolong Cc: Ferruh Yigit , dev@dpdk.org Date: Wed, 03 Apr 2019 15:51:46 +0100 In-Reply-To: <20190403144327.GB36385@intel.com> References: <20190402154653.711-1-xiaolong.ye@intel.com> <20190402154653.711-2-xiaolong.ye@intel.com> <20190403095939.GA32340@intel.com> <56ce5855b02d47a085a8d36451561c400f0b039c.camel@debian.org> <0dde8c20e9992047f29d39ad45dcf511244a5297.camel@debian.org> <80c81c0c-cf64-59f8-a592-26cd865fbd89@intel.com> <37073834d0b9a9f5a6e9f39bac3adc5eb29779ab.camel@debian.org> <5bc49c51-04f4-6f73-889d-d3c0ff749784@intel.com> <46d92b70a40581462f5ee3ba301c793c4cf0c2df.camel@debian.org> <20190403144327.GB36385@intel.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.30.5-1 MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v9 1/1] net/af_xdp: introduce AF XDP PMD driver 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: <20190403145146.fKIvOmaoy29zqxWYW8O0tiaEo49ZsqvGP5KC82mUj0M@z> On Wed, 2019-04-03 at 22:43 +0800, Ye Xiaolong wrote: > On 04/03, Luca Boccassi wrote: > [snip] > > > Got it. > > >=20 > > > In above steps, 'libbpf' also build from kernel source tree, will > > > it > > > be problem > > > in you builds to not have it build from source? > > >=20 > > > If not, taking into account that xsk.h also will be fixed, only > > > 'tools/include/asm/barrier.h' remains the problem, and it looks > > > like > > > it can be > > > solved, please check above. > >=20 > > libbpf is already packaged separately in Debian and I think other > > distros will follow soon, so it's all good for me once the barrier > > issue is solved. > >=20 > > https://packages.debian.org/buster/libbpf-dev > >=20 > >=20 > > From the makefile's perspective it should not matter where it comes > > from - the headers should be expected to be in /usr/include and the > > library in /usr/lib* - and pkg-config can help with that if > > available. > > And if a user wants to use a custom path, then it's no different > > than > > any of the other dependencies on other external libraries >=20 > From tools/lib/bpf/Makefile, after make install_lib and make > install_headers, > the headers and library would be put in /usr/local/include/bpf and > /usr/local/lib*, > Is it ok? Yes certainly that's fine, that's expected for local installations, and users can specify a prefix with the upstream's makefile if they want to install somewhere else. --=20 Kind regards, Luca Boccassi