From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id C9ABDB368 for ; Tue, 9 Sep 2014 22:42:10 +0200 (CEST) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 41C9B80C76D; Tue, 9 Sep 2014 13:47:02 -0700 (PDT) Date: Tue, 9 Sep 2014 13:47:02 -0700 From: Matthew Hall To: Stephen Hemminger Message-ID: <20140909204702.GB11510@mhcomputing.net> References: <4a71bb41.1307.14857e341d5.Coremail.zimeiw@163.com> <20140909062016.GA7050@mhcomputing.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) 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 20:42:11 -0000 On Tue, Sep 09, 2014 at 07:54:19AM -0700, Stephen Hemminger 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. It would be a can of worms for a closed-source app. Which is why some others have used the BSD stack. But it doesn't mean it isn't useful code. Matthew.