From: Matthew Hall <mhall@mhcomputing.net>
To: "Zhang, Helin" <helin.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] TCP/IP stack for DPDK
Date: Mon, 8 Sep 2014 23:58:53 -0700 [thread overview]
Message-ID: <20140909065852.GB7240@mhcomputing.net> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A784F23@SHSMSX104.ccr.corp.intel.com>
On Tue, Sep 09, 2014 at 06:47:48AM +0000, Zhang, Helin wrote:
> That means your great works under GPL/LGPL license will not occur in DPDK main line, as it is always BSD license.
>
> Regards,
> Helin
However despite this issue, there are some cases where the Linux stack is
greatly superior to the BSD one although normally the opposite is the case...
AF_NETLINK for configuring 10,000+ IP addresses, especially for L4-L7
performance testing, would be one possible example of this. Another potential
example would be the BPF JIT compiler if you want to combine BPF filters with
DPDK (something I'm doing right now in my own code actually).
Matthew.
next prev parent reply other threads:[~2014-09-09 6:54 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 [this message]
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
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=20140909065852.GB7240@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.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).