From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] net/tap: fix build issue with ARM32 Date: Wed, 31 Jan 2018 12:19:06 +0100 Message-ID: <1814250.kpiQluYUny@xps> References: <20180131051408.3652-1-jerin.jacob@caviumnetworks.com> <20180131102352.GA24477@jerin> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Jerin Jacob , Pascal Mazon , Jan Viktorin , Jianbo Liu To: Ophir Munk Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 763FB1B759 for ; Wed, 31 Jan 2018 12:19:53 +0100 (CET) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 31/01/2018 11:38, Ophir Munk: > From: Jerin Jacob [mailto:jerin.jacob@caviumnetworks.com] > > > arm architecture is missing is file drivers/tap/tap_bpf.h I suggest > > > adding it, for example > > > > > > # elif defined(__arm__) > > > # define __NR_bpf 386 [...] > > I am not sure, Is eBPF support available for arm32 support? > > TAP eBPF has a graceful approach: it must successfully compile on all Linux > distributions. If a specific kernel cannot support eBPF it will gracefully > refuse the eBPF netlink message sent to it. > Thus, there is no harm even if there is no eBPF support available for arm32. > > You should enable TAP compilation for cases where you only need TAP without eBPF. Ophir, please send a patch.