From: Matthew Hall <mhall@mhcomputing.net>
To: Jim Thompson <jim@netgate.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] TCP/IP stack for DPDK
Date: Tue, 9 Sep 2014 13:51:14 -0700 [thread overview]
Message-ID: <20140909205114.GC11510@mhcomputing.net> (raw)
In-Reply-To: <E58E79CA-33ED-4104-A9C3-BFA738D24C6E@netgate.com>
On Tue, Sep 09, 2014 at 08:00:32AM -0700, Jim Thompson wrote:
> BPF JIT, or even pflua[1] should be straight-forward to put on top of DPDK.
> (It’s straight-forward to do on top of netmap.)
>
> jim
The pflua guys made a user-space copy of Linux BPF JIT. I'm planning to use
that because it was almost as fast as pflua with a lot fewer usage headaches
and dependencies.
I'm making an MIT licensed app... so it isn't an issue for me personally if
there is some GPL2 Linux code present. I don't think anybody made a non-rump
version of the BSD one yet or I'd use that... I'm trying not to stray too far
from the app's original purposes until it has some working features present.
Until that time comes, I just started out with libpcap offline mode BPF for
development purposes because it's standard and already available, and allows
operations upon raw packet pointers with no issues at all.
Matthew.
next prev parent reply other threads:[~2014-09-09 20:46 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
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 [this message]
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=20140909205114.GC11510@mhcomputing.net \
--to=mhall@mhcomputing.net \
--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).