General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] high speed packet and protocol processing in userspace?
Date: Thu, 16 Mar 2017 11:52:29 -0400	[thread overview]
Message-ID: <27209.1489679549@obiwan.sandelman.ca> (raw)
In-Reply-To: <CAA93jw4NwDODy7yxT-Eu38p_M8YPbNTLysB36_K-1dtcMj6sdA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]


Dave Taht <dave.taht@gmail.com> wrote:
    > Is it faster to execute 17 bpf vm instructions on (nearly) every
    > packet, or to use all that old stuff?

    > bpf example for the babel protocol:

I have no data for you.  Andrew McGregor might know more?
My understanding is that there is a JIT for ebpf.

    > B) Are there any means of easily abstracting deeper protocol processing
    > into a higher level grammar, better than tcpdump? I found one tool,
    > that I like conceptually - for deeply decoding a protocol -

tcpdump just exposes the libpcap compiler.  It has many annoying limitations.

    > I've googled, and thunk, and maybe I'm merely asking the wrong
    > questions, and "the packet analysis tool to end all tools" already
    > exists?

Yes, people have produced them, but they go nowhere because they are too
specialized, or too general.  The question is: are you trying to build a tcp
stack that punts packets at applications, or do "analysis" --- which I interpret
to mean to collect statistics.

    > C) Are vendors like mellonox or others doing network offloads parsing
    > bpf or ebpf directly yet?

I don't know.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2017-03-16 15:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16 15:19 Dave Taht
2017-03-16 15:52 ` Michael Richardson [this message]
2017-03-16 16:27   ` Eric Dumazet
2017-03-16 16:44     ` Dave Taht
2017-03-16 17:32       ` Michael Richardson
2017-03-16 20:04         ` Dave Taht
2017-03-17  9:02     ` Jesper Dangaard Brouer
2017-03-17 12:10       ` Daniel Borkmann
2017-03-17 20:11         ` Jesper Dangaard Brouer

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

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=27209.1489679549@obiwan.sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.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