From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id B64C7A00BE; Wed, 4 May 2022 01:17:24 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8DF8840694; Wed, 4 May 2022 01:17:23 +0200 (CEST) Received: from forward501p.mail.yandex.net (forward501p.mail.yandex.net [77.88.28.111]) by mails.dpdk.org (Postfix) with ESMTP id EB44940691 for ; Wed, 4 May 2022 01:17:21 +0200 (CEST) Received: from vla5-fbe4dab4913c.qloud-c.yandex.net (vla5-fbe4dab4913c.qloud-c.yandex.net [IPv6:2a02:6b8:c18:3607:0:640:fbe4:dab4]) by forward501p.mail.yandex.net (Yandex) with ESMTP id 458C86212210; Wed, 4 May 2022 02:17:21 +0300 (MSK) Received: from vla1-62318bfe5573.qloud-c.yandex.net (vla1-62318bfe5573.qloud-c.yandex.net [2a02:6b8:c0d:3819:0:640:6231:8bfe]) by vla5-fbe4dab4913c.qloud-c.yandex.net (mxback/Yandex) with ESMTP id MHWV8k3KaB-HLgCiHPs; Wed, 04 May 2022 02:17:21 +0300 X-Yandex-Fwd: 2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1651619841; bh=g6XviasirOtiUnRtXRzK4iXnQpaERBV4AJFzAIrtY+Y=; h=In-Reply-To:From:Subject:References:Date:Message-ID:To; b=Rp4WE4tAfnWUguhDe5BrLwaXZbCjxyk0EfGnavKJdU70ciL5gsV4GfCzoMhjLreNg KQbO0fQ6hEiPLjOWH75wgjeoQeQnjWyPIbvyvDKeeWD0U8fwRDDRFDM1VRrC2SVmyJ vPPYWil3EjfRRYz2N5Q/UaNHlZFc4Vh0Qk/RqoHY= Authentication-Results: vla5-fbe4dab4913c.qloud-c.yandex.net; dkim=pass header.i=@yandex.ru Received: by vla1-62318bfe5573.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id uAKQexBGg0-HKMuuf15; Wed, 04 May 2022 02:17:20 +0300 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client certificate not present) Message-ID: <86771c00-4978-3b6f-df5b-187a0a8e9983@yandex.ru> Date: Wed, 4 May 2022 00:17:18 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Subject: Re: librte_bpf: roadmap or any specific plans for this library Content-Language: en-US To: =?UTF-8?Q?Bj=c3=b6rn_Svensson_A?= , "dev@dpdk.org" References: <8e8fcdea-5265-1126-4912-c7fec9b659c4@yandex.ru> From: Konstantin Ananyev In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org >> AFAIK linux BPF is restricted to work with a single argument only. >> I don't want DPDK version to fork too far away from 'canonical' version. >> Though, as I said above, nothing prevents you to create a struct >> with several fields, and pass pointer to that struct to your BPF program. >> Would such approach work for you? > > Good alternative idea. We will test this approach. > I guess we will use the RTE_BPF_ARG_PTR as an argument for the program > in this case. Yes, I believe so. > > Just as sidenote: we have also had a glance at > https://github.com/iovisor/ubpf > as an alternative. This is a standalone BPF VM lib, but with Apache 2.0 > license and it's not bound to the dpdk log framework. > I have no views on benefits using this in dpdk, but it might be an input > for future talks about a common library / collaboration. > > Thanks again. > Bjorn