From: Dor Laor <dor@cloudius-systems.com>
To: Jim Thompson <jim@netgate.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Beyond DPDK 2.0
Date: Tue, 28 Apr 2015 10:20:43 +0300 [thread overview]
Message-ID: <CAKUaUn4Cu9ZwMSkH9P9PstCaDEzifw=zMy5hXPZN1GKbeix7tQ@mail.gmail.com> (raw)
In-Reply-To: <6F92C985-29AC-48D0-A6A5-14738F04E313@netgate.com>
On Mon, Apr 27, 2015 at 5:29 AM, Jim Thompson <jim@netgate.com> wrote:
>
> > On Apr 26, 2015, at 4:56 PM, Neil Horman <nhorman@tuxdriver.com> wrote:
> >
> > On Sat, Apr 25, 2015 at 04:08:23PM +0000, Wiles, Keith wrote:
> >> +1 and besides the GPL or LGPL ship has sailed IMHO and we can not go
> back.
> > Actually, IANAL, but I think we can. The BSD license allows us to fork
> and
> > relicense the code I think, under GPL or any other license. I'm not
> advocating
> > for that mind you, just suggesting that its possible should it ever
> become
> > needed.
>
> I, on the other hand, am fairly certain that you can not “relicense BSD
> licensed code under the GPL (or any other license).
>
> Were this true at law, then the opposite would also be possible. (“Don’t
> like the license? Just fork!”)
>
>
+1
While BSD carries many benefits for DPDK (similar to any other library),
GPL doesn't
carry any benefit in this case. It's not wise not to contribute back to
DPDK regardless
of any license of choice. Those who do not wish to contribute will always
manage to do..
Going back to the list of open source projects on top of DPDK I like to
mention
the SeaStar project:
http://www.seastar-project.org
For those who aren't familiar, SeaStar is a high speed messaging framework
with a unique shared-nothing approach with a per-core granularity.
For our knowledge it offers the first open source TCP/IP implementation on
top
of DPDK along with many other advantages.
DPDK is one of the main building blocks that allow us to reach millions of
iops and we're
pretty pleased with the project - both the source code as well as the
community!
Dor
next prev parent reply other threads:[~2015-04-28 7:20 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 10:38 O'Driscoll, Tim
2015-04-22 15:11 ` O'Driscoll, Tim
2015-04-22 15:33 ` Stephen Hemminger
2015-04-23 11:36 ` O'Driscoll, Tim
2015-04-24 21:02 ` Dave Neary
2015-05-07 14:02 ` Avi Kivity
2015-05-07 14:34 ` Ivan Boule
2015-05-07 15:27 ` Wiles, Keith
2015-05-07 15:33 ` Avi Kivity
2015-05-07 15:33 ` Avi Kivity
2015-05-07 15:49 ` Wiles, Keith
2015-05-07 16:05 ` Avi Kivity
2015-05-08 4:16 ` Wiles, Keith
2015-05-08 5:29 ` Luke Gorrie
2015-05-08 9:06 ` Bruce Richardson
2015-05-08 9:32 ` Luke Gorrie
2015-05-08 9:42 ` Bruce Richardson
2015-05-08 10:02 ` Luke Gorrie
2015-05-08 14:44 ` Wiles, Keith
2015-05-08 16:16 ` Stephen Hemminger
2015-05-08 10:26 ` Hobywan Kenoby
2015-05-08 13:31 ` Neil Horman
2015-05-08 16:22 ` Stephen Hemminger
2015-05-07 15:34 ` Luke Gorrie
2015-05-08 4:31 ` Wiles, Keith
2015-04-24 7:47 ` Luke Gorrie
2015-04-24 15:29 ` O'Driscoll, Tim
2015-04-24 17:00 ` Neil Horman
2015-04-26 9:07 ` Luke Gorrie
2015-04-24 17:39 ` Jay Rolette
2015-04-24 17:51 ` Matthew Hall
2015-04-25 13:30 ` Marc Sune
2015-04-25 16:08 ` Wiles, Keith
2015-04-26 21:56 ` Neil Horman
2015-04-27 2:29 ` Jim Thompson
2015-04-27 13:07 ` Neil Horman
2015-04-27 16:07 ` Stephen Hemminger
2015-04-28 7:20 ` Dor Laor [this message]
[not found] ` <D162FA4E.1DED8%keith.wiles@intel.com>
2015-04-27 9:52 ` Marc Sune
2015-04-27 13:39 ` Wiles, Keith
2015-04-27 15:34 ` Marc Sune
2015-04-27 10:29 ` Neil Horman
2015-04-27 13:50 ` Wiles, Keith
2015-04-27 15:23 ` Neil Horman
2015-04-27 12:38 ` Dave Neary
2015-04-27 13:41 ` Neil Horman
2015-04-27 16:09 ` Stephen Hemminger
2015-04-24 18:12 ` Matt Laswell
2015-04-24 18:51 ` Neil Horman
2015-04-24 19:55 ` Jay Rolette
2015-04-25 12:10 ` Neil Horman
2015-04-27 13:46 ` Jay Rolette
2015-04-28 17:26 ` Neil Horman
2015-04-28 20:02 ` Jay Rolette
2015-04-28 6:22 ` Matthew Hall
2015-04-28 17:48 ` Stephen Hemminger
2015-04-30 21:31 Wiles, Keith
2015-04-30 21:38 ` Wiles, Keith
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='CAKUaUn4Cu9ZwMSkH9P9PstCaDEzifw=zMy5hXPZN1GKbeix7tQ@mail.gmail.com' \
--to=dor@cloudius-systems.com \
--cc=dev@dpdk.org \
--cc=jim@netgate.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).