From: Stephen Hemminger <stephen@networkplumber.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] passing args to bpf programs
Date: Wed, 1 Aug 2018 09:35:22 -0700 [thread overview]
Message-ID: <20180801093522.22c1f043@xeon-e3> (raw)
In-Reply-To: <CAA93jw4YyAfgyFX-6_HTMaCdhfsWVt=V3eQ5uUzH78WuunVLRw@mail.gmail.com>
On Wed, 1 Aug 2018 09:22:41 -0700
Dave Taht <dave.taht@gmail.com> wrote:
> this really isn't the right list for this... but I wanted to build on
> the ack_filter bpf code I had, to create impairments, like dropping
> acks every X packets, or randomly, or when a specific pattern is seen
> (like timestamps or sack). This was sort of the reverse complement to
> getting the cake ack-filter right, now that I know everything that can
> go wrong...
>
> I see I can return ACT_SHOT, so I can drop packets.
>
> But what I can't quite figure out is how to pass args to an tc ebpf
> program. Do I have to pass those via a file descriptor? A map
> generated elsewhere? what? Sure as heck don't want to compile one
> program per opt....
>
> Simplest args would be:
>
> max 16 - drop every 16th ack packet
> random 24 - drop randomly between 0 24
> match only certain flags
>
> followed by more gnarly ones like:
>
> miscalculate if I have a payload or not
> drop sack
> mangle timestamps
>
With Xnetem, I ended up creating a map of config options.
next prev parent reply other threads:[~2018-08-01 16:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 16:22 Dave Taht
2018-08-01 16:35 ` Stephen Hemminger [this message]
2018-08-01 16:36 ` Dave Taht
2018-08-01 16:42 ` Jonathan Morton
2018-08-01 16:54 ` Dave Taht
2018-08-01 17:25 ` Dave Taht
2018-08-01 19:20 ` [Cake] codel in ebpf? Dave Taht
2018-08-02 20:04 ` Toke Høiland-Jørgensen
2018-08-03 0:22 ` Dave Taht
2018-08-03 10:19 ` Toke Høiland-Jørgensen
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180801093522.22c1f043@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=cake@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