From: Jakub Kicinski <kuba@kernel.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: davem@davemloft.net, daniel@iogearbox.net, andrii@kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH bpf-next] bpf: Document BPF licensing.
Date: Thu, 16 Sep 2021 07:06:32 -0700 [thread overview]
Message-ID: <20210916070632.2ee005e7@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20210916032104.35822-1-alexei.starovoitov@gmail.com>
On Wed, 15 Sep 2021 20:21:04 -0700 Alexei Starovoitov wrote:
> +In HW
> +-----
> +
> +The HW can choose to execute eBPF instruction natively and provide eBPF runtime
> +in HW or via the use of implementing firmware with a proprietary license.
That seems like a step back, nfp parts are all BSD licensed:
https://github.com/Netronome/nic-firmware/blob/master/firmware/apps/nic/ebpf.uc
> +Packaging BPF programs with user space applications
> +====================================================
> +
> +Generally, proprietary-licensed applications and GPL licensed BPF programs
> +written for the Linux kernel in the same package can co-exist because they are
> +separate executable processes. This applies to both cBPF and eBPF programs.
Interesting. BTW is there a definition of what "executable process" is?
But feel free to ignore, I appreciate that polishing legalese is not
what you want to spend you time doing. Much less bike shedding about
it. Mostly wanted to mention the nfp part :)
next prev parent reply other threads:[~2021-09-16 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 3:21 [PATCH bpf-next] bpf: Document BPF licensing Alexei Starovoitov
2021-09-16 5:01 ` Stephen Hemminger
2021-09-16 7:29 ` Simon Horman
2021-09-16 7:49 ` Jesper Dangaard Brouer
2021-09-16 14:06 ` Jakub Kicinski [this message]
2021-09-16 20:04 ` Alexei Starovoitov
2021-09-16 16:05 ` Jonathan Corbet
2021-09-16 20:49 ` Alexei Starovoitov
2021-09-17 16:42 ` KP Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210916070632.2ee005e7@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.