From: Matthias Tafelmeier <matthias.tafelmeier@gmx.net>
To: Dave Taht <dave@taht.net>
Cc: Bob Briscoe <ietf@bobbriscoe.net>,
ken@cs.cornell.edu, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] DETNET
Date: Sat, 18 Nov 2017 16:38:52 +0100 [thread overview]
Message-ID: <a86d8ba8-9c4f-ebe9-c4ad-ef1996a8c225@gmx.net> (raw)
In-Reply-To: <87fu9f72za.fsf@nemesis.taht.net>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 1388 bytes --]
On 11/15/2017 08:31 PM, Dave Taht wrote:
>> However, like you, I just sigh when I see the behemoth detnet is building.
>>
>> Does it? Well, so far the circumference seems justififiable for what they want
>> to achieve, at least according to what I can tell from these rather still
>> abstract concepts.
>>
>> The sort of industrial control applications that detnet is targeting
>> require far lower queuing delay and jitter than fq_CoDel can give. They
>> have thrown around numbers like 250us jitter and 1E-9 to 1E-12 packet
>> loss probability.
>>
>> Nonetheless, it's important to have a debate about where to go to next.
>> Personally I don't think fq_CoDel alone has legs to get (that) much better.
> The place where bob and I always disconnect is that I care about
> interflow latencies generally more than queuing latencies and prefer to
> have strong incentives for non-queue building flows in the first
> place. This results in solid latencies of 1/flows at your bandwidth. At
> 100Mbit, a single 1500 byte packet takes 130us to deliver, gbit, 13us,
> 10Gbit, 1.3us.
A not necessarily informed enough question to that: couldn't this
marking based virtual queueuing get extended to a per flow mechanism if
the marking loop was implemented in an efficient way?
--
Besten Gruß
Matthias Tafelmeier
[-- Attachment #1.1.1.2: Type: text/html, Size: 1862 bytes --]
[-- Attachment #1.1.2: 0x8ADF343B.asc --]
[-- Type: application/pgp-keys, Size: 4806 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 538 bytes --]
next prev parent reply other threads:[~2017-11-18 15:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 13:45 Matthias Tafelmeier
[not found] ` <87shdr0vt6.fsf@nemesis.taht.net>
2017-11-12 14:58 ` Matthias Tafelmeier
2017-11-12 19:58 ` Bob Briscoe
2017-11-13 17:56 ` Matthias Tafelmeier
2017-11-15 19:31 ` Dave Taht
2017-11-15 19:45 ` Ken Birman
2017-11-15 20:09 ` Matthias Tafelmeier
2017-11-15 20:16 ` Dave Taht
2017-11-15 21:01 ` Ken Birman
2017-11-18 15:56 ` Matthias Tafelmeier
2017-12-11 20:32 ` Toke Høiland-Jørgensen
2017-12-11 20:43 ` Ken Birman
2017-11-18 15:38 ` Matthias Tafelmeier [this message]
2017-11-18 15:45 ` Ken Birman
2017-11-19 18:33 ` Dave Taht
2017-11-19 20:24 ` Ken Birman
2017-11-20 17:56 ` [Bloat] *** GMX Spamverdacht *** DETNET Matthias Tafelmeier
2017-11-20 19:04 ` Ken Birman
2017-12-17 12:46 ` Matthias Tafelmeier
2017-12-17 16:06 ` Ken Birman
2017-11-18 17:55 ` [Bloat] DETNET Matthias Tafelmeier
2017-11-18 19:43 ` Ken Birman
2017-11-18 19:47 ` Ken Birman
2017-11-20 18:32 ` Matthias Tafelmeier
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a86d8ba8-9c4f-ebe9-c4ad-ef1996a8c225@gmx.net \
--to=matthias.tafelmeier@gmx.net \
--cc=bloat@lists.bufferbloat.net \
--cc=dave@taht.net \
--cc=ietf@bobbriscoe.net \
--cc=ken@cs.cornell.edu \
/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