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 987CDA2F67 for ; Fri, 4 Oct 2019 12:53:12 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 7B3351C1EA; Fri, 4 Oct 2019 12:53:12 +0200 (CEST) Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) by dpdk.org (Postfix) with ESMTP id 2C4A61C1DE for ; Fri, 4 Oct 2019 12:53:11 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id 5BBF84CAF; Fri, 4 Oct 2019 06:53:10 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 04 Oct 2019 06:53:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=3KXwb3hv6Eu2ARN0uhQ7zguo8/YYRy1xcAybNnw/KAw=; b=KTK7EGo0Vef4 ijwgrs5+8XjJ/uOPVQQVLUUkBll2DuOC6877P7yVJN/VZlP1+w+TKFmAtNg6zlw8 UECbz9FxcshPbaQncwjIAlZqwNcef8c8h8jY3h+Stil5bwd8Z67AqiWRAc4oSLsL lLqmqbvw+1qVT4OWexgL/A1tfIIq1C0= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=3KXwb3hv6Eu2ARN0uhQ7zguo8/YYRy1xcAybNnw/K Aw=; b=AwNNh8jxkcEg7FkqTrbssU2gzcUw/FuwMf8Zci5T1jcdW/O5Gd4UNSGyJ VLZlthLB3A23mHcK/zgwzpzZxb/pRSmy1wLmc9DPjZvKwzEa/x338lSuyWMiRoMN lFVSpEXwSBDtgrFXze4fxBs91IBu1eb49eiKmQkRCEbz+Qyq9D0ekH6xQGJlDfdo W+Be7t9xo4XZvXvLIBGOeYeIwgFvLkjCMuJEmi+BgIgTawrtxg4haXZyzlc4EvBk Wq4uF5AnUHjVuQU+MmfiR+S6RKn7YacDrl7+X2LcBh5gPvAT0MpHradgL2cBp4vu vrE1T1Mxp1LyuJvTNHJfYVNxyO2jQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrhedugddvjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 1D698D6005B; Fri, 4 Oct 2019 06:53:08 -0400 (EDT) From: Thomas Monjalon To: Steve Capper , "Ananyev, Konstantin" , Jerin Jacob Cc: Honnappa Nagarahalli , Rodolph Perfetta , "jerinj@marvell.com" , dev@dpdk.org, "Gavin Hu (Arm Technology China)" , nd , Alexei Starovoitov , Daniel Borkmann , Quentin Monnet Date: Fri, 04 Oct 2019 12:53:06 +0200 Message-ID: <2296691.KpWsp5kHI9@xps> In-Reply-To: <20191004095455.GA17770@capper-ampere.manchester.arm.com> References: <20190903105938.33231-1-jerinj@marvell.com> <20191004095455.GA17770@capper-ampere.manchester.arm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 0/8] eBPF arm64 JIT support 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" 04/10/2019 11:54, Steve Capper: > I'd recommend also reaching out the BPF maintainers: > BPF JIT for ARM64 > M: Daniel Borkmann > M: Alexei Starovoitov > M: Zi Shen Lim > L: netdev@vger.kernel.org > L: bpf@vger.kernel.org > S: Supported > F: arch/arm64/net/ > > As they will have much better knowledge of the state of play and will be > better able to advise. As far as I know Alexei and Daniel are OK with the idea. But better to let them reply here. I suggest we think about a way to package the kernel BPF JIT for userspace usage (not only DPDK) as a library. I don't understand why the DPDK JIT should be different or optimized differently. The only real issue I see is the need for a dual licensing BSD-GPL.