From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Fwd: [Codel] fq_codel_drop vs a udp flood
Date: Fri, 6 May 2016 07:44:23 +0300 [thread overview]
Message-ID: <1577AB06-3C14-43D1-92AD-E37CEDCB8E11@gmail.com> (raw)
In-Reply-To: <CAA93jw58RDSM82VvuQJwza84gQn03ZRJrgHr7F1sDnVsyQeqkQ@mail.gmail.com>
> On 6 May, 2016, at 07:35, Dave Taht <dave.taht@gmail.com> wrote:
>
> this would be a pretty nifty feature for cake to have in this hostile universe.
Yes, but difficult to implement since the trailing fragments lose the proto/port information, and thus get sorted into a different queue than the leading fragment. We would essentially need to implement the same tracking mechanisms as for actual reassembly.
- Jonathan Morton
next prev parent reply other threads:[~2016-05-06 4:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA93jw6QLyx9EaS+ntB0D3duoysu_Z-UYyQfHnRa=pfqPDfWOw@mail.gmail.com>
[not found] ` <1462125592.5535.194.camel@edumazet-glaptop3.roam.corp.google.com>
[not found] ` <865DA393-262D-40B6-A9D3-1B978CD5F6C6@gmail.com>
[not found] ` <1462128385.5535.200.camel@edumazet-glaptop3.roam.corp.google.com>
[not found] ` <C5D365DA-18EE-446E-9D25-41F48B1C583E@gmail.com>
[not found] ` <1462136140.5535.219.camel@edumazet-glaptop3.roam.corp.google.com>
[not found] ` <CACiydbKUu11=zWitkDha0ddgk1-G_Z4-e1+=9ky776VktF5HHg@mail.gmail.com>
[not found] ` <1462201620.5535.250.camel@edumazet-glaptop3.roam.corp.google.com>
[not found] ` <CACiydbKeKUENncrc-NmYRcku-DGVeGqqzYMqsCqKdxPsR7yUOQ@mail.gmail.com>
[not found] ` <1462205669.5535.254.camel@edumazet-glaptop3.roam.corp.google.com>
[not found] ` <CACiydbL26Jj3EcEL4EmqaH=1Dm-Q0dpVwoWxqUSZ7ry10bRgeg@mail.gmail.com>
[not found] ` <CAA93jw5Y3DSzuOZo=S6_dsUqJvy_3ThNe6tMic2ZJ14kQPnFHg@mail.gmail.com>
[not found] ` <CACiydb+kOLNBwEn+gDU3fZrXEQxp5FMFLH_mDS1ZO5J8r9yiBA@mail.gmail.com>
[not found] ` <2D83E4F6-03DD-4421-AAE0-DD3C6A8AFCE0@gmail.com>
[not found] ` <CAA93jw6Aj3Rcsm=Q=KZVrW_TGThVwu6pRAN3nNQ4tvSODY_zUg@mail.gmail.com>
2016-05-06 4:35 ` Dave Taht
2016-05-06 4:44 ` Jonathan Morton [this message]
2016-05-06 4:57 ` Dave Taht
2016-05-06 8:49 ` moeller0
2016-05-06 9:00 ` David Lang
2016-05-06 9:36 ` moeller0
2016-05-06 15:31 ` Stephen Hemminger
2016-05-06 18:50 ` David Lang
2016-05-06 18:53 ` Jonathan Morton
2016-05-06 19:14 ` David Lang
2016-05-06 19:33 ` Jonathan Morton
2016-05-06 19:54 ` David Lang
2016-05-06 19:58 ` David Lang
2016-05-06 23:14 ` Benjamin Cronce
2016-05-07 2:09 ` David Lang
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=1577AB06-3C14-43D1-92AD-E37CEDCB8E11@gmail.com \
--to=chromatix99@gmail.com \
--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