From: David Ahern <dsahern@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [PATCH iproute2-next] Add tc-BPF example for a TCP pure ack recognizer
Date: Wed, 2 May 2018 09:22:24 -0600 [thread overview]
Message-ID: <d1c86b02-04e8-f02a-2fe6-ac69517e1cf7@gmail.com> (raw)
In-Reply-To: <CAA93jw7d6oiushFda=Z7nY6xCeVFWk9cBcJRUaCtjtCLcfJTXQ@mail.gmail.com>
On 5/1/18 10:51 PM, Dave Taht wrote:
> On Tue, May 1, 2018 at 9:12 PM, David Ahern <dsahern@gmail.com> wrote:
>> On 5/1/18 12:32 PM, Dave Taht wrote:
>>> ack_recognize can shift pure tcp acks into another flowid.
>>> ---
>>> examples/bpf/ack_recognize.c | 98 ++++++++++++++++++++++++++++++++++++++++++++
>>> 1 file changed, 98 insertions(+)
>>> create mode 100644 examples/bpf/ack_recognize.c
>>>
>>> diff --git a/examples/bpf/ack_recognize.c b/examples/bpf/ack_recognize.c
>>> new file mode 100644
>>> index 0000000..5da620c
>>> --- /dev/null
>>> +++ b/examples/bpf/ack_recognize.c
>>> @@ -0,0 +1,98 @@
>>> +/* SPDX-License-Identifier: GPL-2.0 */
>>> +/*
>>> + * Copyright 2017 Google Inc.
>>
>> 2017?? it's 2018. Did you write this last year and just now posting?
>
> November, 2017? Shortly prior to you taking iproute2-next off of steven's hands.
ok, just checking
>
> It was the first stage of a proof of concept showing (eventually) that
> a simple ack decimator/filter (like "drop every other ack", or simple
> "drop head" in the supplied example) had a ton of problems, and that
> to filter out acks correctly to any extent, it needed to peer back
> into the queue. (see the sch_cake ack-filter controversy on-going on
> this list)
>
> While it's better than what is in wondershaper, I wouldn't recommend
> anyone use it. It was, however, useful in acquiring a gut feel for
> what several other broken ack filters might be doing in the field. I
> submitted it as a possibly useful example for showing off tc-bpf and
> to add fuel to the ack-filter fire under cake.
>
> I can clean it up, SPF it, etc, if you want it. Otherwise, sorry for the noise.
I'm fine with the example, just prefer magic numbers to be clarified.
next prev parent reply other threads:[~2018-05-02 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 18:32 [PATCH iproute2-next] Add tc-BPF example for a TCP pure ack recognizer Dave Taht
2018-05-02 4:12 ` David Ahern
2018-05-02 4:51 ` Dave Taht
2018-05-02 15:22 ` David Ahern [this message]
2019-10-21 23:47 ` Stephen Hemminger
2019-10-23 4:59 ` Dave Taht
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=d1c86b02-04e8-f02a-2fe6-ac69517e1cf7@gmail.com \
--to=dsahern@gmail.com \
--cc=dave.taht@gmail.com \
--cc=netdev@vger.kernel.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).