From: Jonathan Morton <chromatix99@gmail.com>
To: Rick Jones <rick.jones2@hpe.com>
Cc: David Lang <david@lang.hm>,
cake@lists.bufferbloat.net, codel@lists.bufferbloat.net
Subject: Re: [Codel] [Cake] Proposing COBALT
Date: Fri, 20 May 2016 19:35:18 +0300 [thread overview]
Message-ID: <26FFB878-5E6B-47B8-8DFD-A8765421655F@gmail.com> (raw)
In-Reply-To: <573F394B.5060009@hpe.com>
> On 20 May, 2016, at 19:20, Rick Jones <rick.jones2@hpe.com> wrote:
>
> On 05/20/2016 08:12 AM, Jonathan Morton wrote:
>>
>>> On 20 May, 2016, at 17:04, David Lang <david@lang.hm> wrote:
>>>
>>> Is it possible to get speed testing software to detect that it's receiving fragments and warn about that?
>>
>> Do iperf3’s maintainers accept patches?
>
> Netperf's maintainer has been known to accept patches so long as they aren't too hairy. That said, it isn't clear how something operating above the socket interface is going to know that the traffic it was receiving was in the form of reassembled IP datagram fragments.
>
> happy benchmarking,
>
> rick jones
>
> I suppose if said software were to dive below the socket interface it could find-out, though that will tend to lack portability.
I’m a little fuzzy on UDP socket semantics.
Could the sender set DF on a small proportion of the packets, and listen for ICMP errors to the effect? These packets could also be salted with distinguishable data so that the receiver can tell whether the DF packets, in particular, got through.
- Jonathan Morton
next prev parent reply other threads:[~2016-05-20 16:35 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 10:04 [Codel] " Jonathan Morton
2016-05-20 11:37 ` [Codel] [Cake] " moeller0
2016-05-20 12:18 ` Jonathan Morton
2016-05-20 13:22 ` moeller0
2016-05-20 14:36 ` Jonathan Morton
2016-05-20 16:03 ` David Lang
2016-05-20 17:31 ` Jonathan Morton
[not found] ` <CALnBQ5mNgHgFoTcvLxppv2P9XODc4D-4NObKyqbZJ0PccVkwiA@mail.gmail.com>
2016-05-20 16:43 ` Jonathan Morton
2016-05-23 18:30 ` Jonathan Morton
2016-05-24 13:47 ` Jeff Weeks
2016-05-24 14:07 ` Jonathan Morton
2016-05-24 15:52 ` Dave Täht
2016-05-24 15:56 ` Jonathan Morton
2016-05-24 16:02 ` Dave Taht
2016-05-26 12:33 ` Jonathan Morton
2016-06-03 19:09 ` Noah Causin
2016-06-03 19:34 ` Jonathan Morton
2016-06-04 1:01 ` Andrew McGregor
2016-06-04 6:23 ` Jonathan Morton
2016-06-04 13:55 ` Jonathan Morton
2016-06-04 14:01 ` moeller0
2016-06-04 14:16 ` Jonathan Morton
2016-06-04 15:03 ` moeller0
2016-06-04 17:10 ` Noah Causin
2016-06-04 17:49 ` Eric Dumazet
2016-06-04 19:55 ` Jonathan Morton
2016-06-04 20:56 ` Eric Dumazet
2016-06-27 3:56 ` Jonathan Morton
2016-06-27 7:59 ` moeller0
2016-05-20 13:41 ` David Lang
2016-05-20 13:46 ` moeller0
2016-05-20 14:04 ` David Lang
2016-05-20 14:42 ` Kathleen Nichols
2016-05-20 15:11 ` Jonathan Morton
2016-05-20 15:12 ` Jonathan Morton
2016-05-20 16:05 ` David Lang
2016-05-20 17:06 ` Jonathan Morton
2016-05-20 16:20 ` Rick Jones
2016-05-20 16:35 ` Jonathan Morton [this message]
2016-05-20 17:01 ` Rick Jones
2016-05-20 17:07 ` Jonathan Morton
2016-05-20 17:21 ` Rick Jones
2016-05-20 17:26 ` David Lang
2016-05-20 17:33 ` Jonathan Morton
2016-05-20 14:09 ` Jonathan Morton
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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=26FFB878-5E6B-47B8-8DFD-A8765421655F@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=rick.jones2@hpe.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