From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f50.google.com (mail-wm0-f50.google.com [74.125.82.50]) by dpdk.org (Postfix) with ESMTP id BE1152A5D for ; Tue, 5 Dec 2017 08:59:23 +0100 (CET) Received: by mail-wm0-f50.google.com with SMTP id t8so10167471wmc.3 for ; Mon, 04 Dec 2017 23:59:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=bmc6X67n8ygMMlQwXuIYw1SayLs9wiG6ZV6fPBcWNkI=; b=W9SxfcDskn1ta3V80UcpZtYPIKfQYsSSk/KWyG2Jl2MLn58jtzveAHEXz+MI5qxZDt lrEKxqRa9v6b865as7+WIIZk6YElwm3V0NxBUDXvcQYqW6AVilOSF+XnEDCb0tWyucnm onMmT0W4rZBUcUpMYzvRDtcGKDrza4Jgm3jwiz99XGZUP2B0vHVOv9313+gESS1eNQNY +Yh/lY9qIKDonF016g3LFxlpnm3+WlULCpaaHUNeLn/Dd0kIBFI7IU8B54TAigyrCXLE 0DjvxE2x9nrUGkusU7ZHkLvEdYVT6p9Gpv3zb3WEcV/DYg7EtXGcTc/zVUz5oc4Z+JCv xIlQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=bmc6X67n8ygMMlQwXuIYw1SayLs9wiG6ZV6fPBcWNkI=; b=Nr/uYOgMqEslgnKwoCqv/PLCFQzLKr8Uu4bwMpMTCGz+DDb2wDcY9DQM0ZSdz9f3+h CszFUNKBLJwfKJ5kAnnTSye6Vrw2dAl7qhKUgZBcMDrtqYze1zBN6CDOpGfMfYMuqD6p 4pa3d5YaPWWqH92vvL+gwY029r7My85rWSbTMbe8DGtq5zvecDiElToqZIXftHBpWqR6 y7NbAwsyCpmNqUYwcggf85FRtGfbhTDzQqDJn6FrbYGv4F/CntR9t6olUION4ScouLXn y4LBlcrp0yKM35J1HVIM0Y5xQpA3HsArmERGzH9mzBMk2yKkA8zZl90x78XCyvVB/Xff ZXeA== X-Gm-Message-State: AJaThX6XfRUgGMbcoXzAczKWBwOW4vnH3Qj1N6rOL/QOH7N4m5PM+d8K UU14cWq3Awz0VsKEmYC4pBVYwg== X-Google-Smtp-Source: AGs4zMaypsgso91VsphaKahgcF0qSA8/HqxINp/v3z+8P3XCiWsmvvF6sCwk9tI5V7XEAEdM6tDd8Q== X-Received: by 10.28.158.212 with SMTP id h203mr10003933wme.157.1512460763469; Mon, 04 Dec 2017 23:59:23 -0800 (PST) Received: from [10.16.18.139] (host.78.145.23.62.rev.coltfrance.com. [62.23.145.78]) by smtp.gmail.com with ESMTPSA id a203sm5496055wmh.45.2017.12.04.23.59.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 04 Dec 2017 23:59:22 -0800 (PST) To: Thomas Monjalon , Stephen Hemminger Cc: dev@dpdk.org, Ophir Munk , Olga Shern References: <1512028870-13597-1-git-send-email-ophirmu@mellanox.com> <33612859.oYs3VmdAvV@xps> <20171130092042.402243a7@xeon-e3> <4022270.ekSSXE0TKz@xps> From: Pascal Mazon Message-ID: <8254049b-9661-3048-756c-b0b1d738885a@6wind.com> Date: Tue, 5 Dec 2017 08:59:23 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <4022270.ekSSXE0TKz@xps> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US Subject: Re: [dpdk-dev] [RFC 2/2] net/tap: add eBPF instructions 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: Tue, 05 Dec 2017 07:59:23 -0000 Indeed, the spirit of the initial work was to publish source code, compiled BPF bytecode, and Makefile for re-generating the latter. I have no clue regarding licensing, I'll trust you guys on that. On 30/11/2017 18:39, Thomas Monjalon wrote: > 30/11/2017 18:20, Stephen Hemminger: >> On Thu, 30 Nov 2017 18:05:22 +0100 >> Thomas Monjalon wrote: >> >>> 30/11/2017 17:54, Stephen Hemminger: >>>> Loading BPF is a could solution to doing dynamic flow matching. >>>> It needs to be done differently to be accepted. >>>> >>>> Putting raw machine instructions in source code is as bad as binary >>>> blobs. You need to provide original source of program and then have >>>> build instructions to create any needed code. >>> The source program is provided in this patch: tap_bpf_program.c >>> It is pre-compiled to avoid requiring too many dependencies when building DPDK. >> But the "freedom to modify" comes into play here. If a *evil* vendor builds >> an application based on DPDK and does not provide source. Then user still deserves >> the right to modify the eBPF program that it loads as GPL. The best solution >> is to make the TAP PMD loader routine load the program from a file. >> Although I am certainly not a FSF legal scholar, putting GPL'd object code in >> TAP PMD risks accusations of being a derived or combined work. > Good point. > The compiled BPF may be provided as a plugin file. > So we would be free to not package this GPL file.