DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jim Thompson <jim@netgate.com>
To: Vadim Suraev <vadim.suraev@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] TCP/IP stack for DPDK
Date: Tue, 9 Sep 2014 08:26:00 -0700	[thread overview]
Message-ID: <BA33F198-66BB-44CB-BEC5-F8902C0A5BA2@netgate.com> (raw)
In-Reply-To: <CAJ0CJ8kvuFzbfyJs+UaaoLq5Y0UJrXe6_V0bK_vLr_RpUyAxGg@mail.gmail.com>

Then you don’t understand licensing.

the GPL has  a requirement that you make one of two offers:

The fourth section for version 2 of the license and the seventh section of version 3 require that programs distributed as pre-compiled binaries are accompanied by a copy of the source code, or a written offer *valid for any third party* to obtain the source code via the same mechanism as the pre-compiled binary.

You can’t sell the source, you have to make it available, either with the binary, or to anyone who asks.

There are other terms and conditions with the GPL (patent licenses, etc.)

Jim

> On Sep 9, 2014, at 8:19 AM, Vadim Suraev <vadim.suraev@gmail.com> wrote:
> 
> The licensing worms prevent IMHO only selling the source code, although,
> porting may be useful
> On Sep 9, 2014 5:54 PM, "Stephen Hemminger" <stephen@networkplumber.org>
> wrote:
> 
>> Porting Linux stack to DPDK opens up a licensing can of worms.
>> Linux code is GPLv2, and DPDK code is BSD. Any combination of the two
>> would end up
>> being covered by the Linux GPLv2 license.
>> 
>> On Mon, Sep 8, 2014 at 11:30 PM, Vadim Suraev <vadim.suraev@gmail.com>
>> wrote:
>> 
>>> I've ported the Linux kernel TCP/IP stack to user space and integrated
>>> with
>>> DPDK,  the source and documentation and the roadmap will be published (and
>>> announced) within few days.
>>> Regards,
>>> Vadim
>>> On Sep 9, 2014 9:20 AM, "Matthew Hall" <mhall@mhcomputing.net> wrote:
>>> 
>>>> On Tue, Sep 09, 2014 at 08:49:44AM +0800, zimeiw wrote:
>>>>> I have porting major FreeBSD tcp/ip stack to dpdk. new tcp/ip stack is
>>>> based
>>>>> on dpdk rte_mbuf, rte_ring, rte_memory and rte_table. it is faster to
>>>>> forwarding packets.
>>>> 
>>>> Hello,
>>>> 
>>>> This is awesome work to be doing and badly needed to use DPDK for any L4
>>>> purposes where it is very limited. I'll be following your progress.
>>>> 
>>>> You didn't mention your name, and compare your work with
>>>> https://github.com/rumpkernel/dpdk-rumptcpip/ , and talk about
>>> behavior /
>>>> performance, and how long you think it'll take. I'm curious if you can
>>> give
>>>> some more comments.
>>>> 
>>>> I'm implementing an RX-side very basic stack myself... but I'm not using
>>>> BSD
>>>> standard APIs or doing TX-side like yours will have.
>>>> 
>>>> Matthew.
>>>> 
>>> 
>> 
>> 

  reply	other threads:[~2014-09-09 15:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09  0:49 zimeiw
2014-09-09  6:20 ` Matthew Hall
2014-09-09  6:30   ` Jim Thompson
2014-09-09  6:30   ` Vadim Suraev
2014-09-09  6:38     ` Zhang, Helin
2014-09-09  6:42       ` Vadim Suraev
2014-09-09  6:47         ` Zhang, Helin
2014-09-09  6:58           ` Matthew Hall
2014-09-09 12:16             ` Alexander Nasonov
2014-09-09 15:00               ` Jim Thompson
2014-09-09 20:17                 ` Alexander Nasonov
2014-09-09 20:51                 ` Matthew Hall
2014-09-09 21:30                   ` Alexander Nasonov
2014-09-09 21:59                     ` Matthew Hall
2014-09-09 22:47                       ` Alexander Nasonov
2014-09-09 14:54     ` Stephen Hemminger
2014-09-09 15:19       ` Vadim Suraev
2014-09-09 15:26         ` Jim Thompson [this message]
2014-09-09 15:59           ` Vadim Suraev
2014-09-09 20:47       ` Matthew Hall
2014-09-09  7:30   ` zimeiw
2014-09-09 16:09 ` Jeff Shaw
2014-09-09 21:49   ` Aaro Koskinen
2014-09-10  3:42     ` zimeiw

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=BA33F198-66BB-44CB-BEC5-F8902C0A5BA2@netgate.com \
    --to=jim@netgate.com \
    --cc=dev@dpdk.org \
    --cc=vadim.suraev@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).