From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] eBPF filters for traffic classification?
Date: Thu, 11 Dec 2014 16:50:31 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1412111647530.14535@nftneq.ynat.uz> (raw)
In-Reply-To: <CAA93jw5mp0uNY5Z5sM5QC6cE8LZPSK_jaZGWt+W0LrHUcBzCtw@mail.gmail.com>
In part, I was thinking that this sort of thing could make experimenting with
codel or HTB tweaks much easier. If the classification logic could be written to
be compiled into eBPF filters, then changing the classification would be just
loading a new module. And since it's compiled and loaded into the kernel, I'm
hoping that the performance would be on the same order as C code (even though
it's interpreted by the eBPF engine), so it wouldn't have the large performance
hit that we have with the current throttling code for example.
David Lang
On Thu, 11 Dec 2014, Dave Taht wrote:
> oh the bpf stuff and jit work is extremely interesting. There is a
> llvm compiler for it too, now.
>
> nftables is also interesting but hard to wrap my head around and
> expressing things in it seems only slightly less hard that just
> adopting bpf directly.
>
> On Thu, Dec 11, 2014 at 4:28 PM, David Lang <david@lang.hm> wrote:
>> http://lwn.net/SubscriberLink/625224/2edd6566c16cf76d/
>>
>> A new capability is being added to the 3.19 kernel that allows writing BPF
>> programs that run in the kernel that can do things like classifying traffic.
>> Right now all this can do is to store information to be retrieved by
>> userspace, but I wonder if it would be useful to use something like this for
>> traffic classification for queue selection, traffic throttling, etc?
prev parent reply other threads:[~2014-12-12 0:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 0:28 David Lang
2014-12-12 0:44 ` Dave Taht
2014-12-12 0:50 ` David Lang [this message]
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1412111647530.14535@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=cerowrt-devel@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