From: Daniel Borkmann <dborkman@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: gregkh@linuxfoundation.org, stephen@networkplumber.org,
netdev@vger.kernel.org, Eric Leblond <eric@regit.org>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [RFC 1/2] netmap: infrastructure (in staging)
Date: Sat, 20 Apr 2013 13:31:02 +0200 [thread overview]
Message-ID: <51727C76.6010501@redhat.com> (raw)
In-Reply-To: <20130419.155859.1092595631804890737.davem@davemloft.net>
On 04/19/2013 09:58 PM, David Miller wrote:
> From: Greg KH <gregkh@linuxfoundation.org>
> Date: Fri, 19 Apr 2013 12:45:37 -0700
>
>> On Fri, Apr 19, 2013 at 12:06:51PM -0700, Stephen Hemminger wrote:
>>> Netmap is a framework for packet generation and capture from user
>>> space. It allows for efficient packet handling (up to line rate on
>>> 10Gb) with minimum system load. For more info see:
>>> http://info.iet.unipi.it/~luigi/netmap/
>
> So are you saying that people can't get line rate today?
>
> Even the the suricata folks are doing deep packet inspection at line
> rate using AF_PACKET fanouts just fine. That means they aren't just
> grabbing packets, they are actually processing them and making
> stateful decisions based upon the packet's contents.
>
> That means that capture is cheap enough already that they have all
> the compute left over that they need.
>
> The existing mechanisms also have the huge advantage that they are
> already implemented, require zero driver specific changes, and are
> already starting to be deployed to end users.
+1, and if so, then I'm actually rather for further improving/optimizing/..
AF_PACKET. Btw., Eric had a blog post from 2012 about this topic (and
maybe TPACKET_V3 could even further improve perf. over TPACKET_V2 on this):
https://home.regit.org/2012/07/suricata-to-10gbps-and-beyond/
Also, I just looked over Netmap's Usenix paper from 2012, where they compare
netmap against pktgen, and while they state the version of the FreeBSD kernel
where they did the evaluation on, they just don't even mention the Linux'
kernel version, their Linux kernel setup etc. Not even mentioning a comparison
of PF_PACKET+fanout (similarly as the PF_RING project seems to avoid this
comparison and only presents perf numbers where they just count packets !).
Also, I've seen other papers published in 2012 on this topic, where they
compare performance with a 2.6.2x kernel, hm, quite sad actually.
next prev parent reply other threads:[~2013-04-20 11:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 19:06 [RFC 1/2] netmap: infrastructure (in staging) Stephen Hemminger
2013-04-19 19:09 ` [RFC 2/2] ixgbe: netmap support Stephen Hemminger
2013-04-19 19:45 ` [RFC 1/2] netmap: infrastructure (in staging) Greg KH
2013-04-19 19:58 ` David Miller
2013-04-19 20:16 ` Stephen Hemminger
2013-04-19 20:31 ` Eric Dumazet
2013-04-19 20:38 ` David Miller
2013-04-19 20:49 ` Stephen Hemminger
2013-04-19 20:53 ` David Miller
2013-05-07 17:20 ` chetan loke
2013-04-19 20:37 ` David Miller
2013-04-20 11:31 ` Daniel Borkmann [this message]
2013-04-20 14:57 ` Jamal Hadi Salim
2013-04-20 15:19 ` "Oleg A. Arkhangelsky"
2013-04-28 22:33 ` Willy Tarreau
2013-04-20 23:20 ` Vincent JARDIN
2013-04-23 7:04 ` Naoto MATSUMOTO
2013-04-23 7:10 ` David Miller
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=51727C76.6010501@redhat.com \
--to=dborkman@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=eric@regit.org \
--cc=gregkh@linuxfoundation.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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).