From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f43.google.com (mail-pa0-f43.google.com [209.85.220.43]) by dpdk.org (Postfix) with ESMTP id B0518AF87 for ; Tue, 9 Sep 2014 17:20:58 +0200 (CEST) Received: by mail-pa0-f43.google.com with SMTP id fa1so4966475pad.16 for ; Tue, 09 Sep 2014 08:26:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=+54cNRdU1a2B+ooYXKDlYRvKv9wW1w1lU7rX0CU/xJs=; b=GTgnSiUz0+EpvzHs1mQMD9TK7f4gCc5P/qljnNJAL88DrCNft+aFXL7TGrSK7hhX6h LT5X8/rFM+8ZnwWFZZIXhi78aEzZcr7uqDhW9Dxmhwh0SD43cdN9ltjL5bplKnlifHQA Vu3PahdKTyhdQbultpmA7iFyjupOisRLDSDDiaTBjrLs/FWe6IZVNDjWITg1dtQhPjso ZMCJY9qeoz3i0iJn3yl64cJ8o5+dwC62H+y6wWYB1Qoa8pQNz6VKZ13ZwDgIXjHxrHg6 5e+1VKDOvfNQOOCVLZHx/yAAxM3Ph+HAH3NTwkFa+a1hn6fIJPWZECOwvaaIKzWI9+fp xRLw== X-Gm-Message-State: ALoCoQl7GuUr4v2pgzm6awqu+OWQLIZIRO2VoXIoLZrZLjY1iFiI40ssDnU3oCxwe6K8zP+3Hcb/ X-Received: by 10.70.37.33 with SMTP id v1mr16676831pdj.155.1410276362447; Tue, 09 Sep 2014 08:26:02 -0700 (PDT) Received: from [172.20.12.149] ([12.232.194.107]) by mx.google.com with ESMTPSA id x3sm9377594pdq.10.2014.09.09.08.26.01 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Sep 2014 08:26:01 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1974.6\)) From: Jim Thompson In-Reply-To: Date: Tue, 9 Sep 2014 08:26:00 -0700 Message-Id: References: <4a71bb41.1307.14857e341d5.Coremail.zimeiw@163.com> <20140909062016.GA7050@mhcomputing.net> To: Vadim Suraev X-Mailer: Apple Mail (2.1974.6) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: dev@dpdk.org Subject: Re: [dpdk-dev] TCP/IP stack for DPDK X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2014 15:20:59 -0000 Then you don=E2=80=99t 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=E2=80=99t 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 = wrote: >=20 > The licensing worms prevent IMHO only selling the source code, = although, > porting may be useful > On Sep 9, 2014 5:54 PM, "Stephen Hemminger" = > wrote: >=20 >> 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. >>=20 >> On Mon, Sep 8, 2014 at 11:30 PM, Vadim Suraev = >> wrote: >>=20 >>> 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" = wrote: >>>=20 >>>> 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. >>>>=20 >>>> Hello, >>>>=20 >>>> 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. >>>>=20 >>>> 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. >>>>=20 >>>> 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. >>>>=20 >>>> Matthew. >>>>=20 >>>=20 >>=20 >>=20