From: Vadim Suraev <vadim.suraev@gmail.com>
To: "Zhang, Helin" <helin.zhang@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] TCP/IP stack for DPDK
Date: Tue, 9 Sep 2014 09:42:43 +0300 [thread overview]
Message-ID: <CAJ0CJ8mz9FpdvMtB2Xnjd+59+LKM8c4mja1VjGQRqndOy2cDLw@mail.gmail.com> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A784F02@SHSMSX104.ccr.corp.intel.com>
IMHO, since GPL is more restrictive so the source must remain open
On Sep 9, 2014 9:39 AM, "Zhang, Helin" <helin.zhang@intel.com> wrote:
>
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Vadim Suraev
> > Sent: Tuesday, September 9, 2014 2:30 PM
> > To: Matthew Hall
> > Cc: dev@dpdk.org
> > Subject: Re: [dpdk-dev] TCP/IP stack for DPDK
> >
> > 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.
>
> Any license issue of porting Linux kernel stack into DPDK?
>
> > 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.
> > >
>
> Regards,
> Helin
>
next prev parent reply other threads:[~2014-09-09 6:37 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 [this message]
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
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=CAJ0CJ8mz9FpdvMtB2Xnjd+59+LKM8c4mja1VjGQRqndOy2cDLw@mail.gmail.com \
--to=vadim.suraev@gmail.com \
--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).