From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: codel@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net,
Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [Codel] happy 4th!
Date: Tue, 09 Jul 2013 15:25:02 +0200 [thread overview]
Message-ID: <87zjtvvpap.fsf@toke.dk> (raw)
In-Reply-To: <1373376239.4979.150.camel@edumazet-glaptop> (Eric Dumazet's message of "Tue, 09 Jul 2013 06:23:59 -0700")
[-- Attachment #1: Type: text/plain, Size: 396 bytes --]
Eric Dumazet <eric.dumazet@gmail.com> writes:
> Its really too basic for my needs.
>
> It decides to put the new packet at the front of transmit queue.
Right I see.
> If you use netem to add a delay, then adding reordering is only a
> matter of using a variable/randomized delay.
Yeah, realised that; was just wondering why you found the built-in
reordering mechanism insufficient. :)
-Toke
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2013-07-09 13:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA93jw7WPdxKwGGvQoSEfmDN3ey9j7+BNT5yohB6XUyCqbQRtQ@mail.gmail.com>
[not found] ` <alpine.DEB.2.00.1307040751130.10894@uplift.swm.pp.se>
[not found] ` <1373223178.486913695@apps.rackspace.com>
[not found] ` <alpine.DEB.2.00.1307080211340.10894@uplift.swm.pp.se>
[not found] ` <871u79x9kb.fsf@toke.dk>
[not found] ` <alpine.DEB.2.00.1307090749480.8891@uplift.swm.pp.se>
2013-07-09 6:32 ` [Codel] [Cerowrt-devel] " Dave Taht
2013-07-09 7:30 ` Andrew McGregor
2013-07-09 13:09 ` Eric Dumazet
2013-07-09 7:57 ` [Codel] " Toke Høiland-Jørgensen
2013-07-09 12:56 ` Eric Dumazet
2013-07-09 13:13 ` Toke Høiland-Jørgensen
2013-07-09 13:23 ` Eric Dumazet
2013-07-09 13:25 ` Toke Høiland-Jørgensen [this message]
2013-07-09 13:36 ` Eric Dumazet
2013-07-09 13:45 ` Toke Høiland-Jørgensen
2013-07-09 13:49 ` Eric Dumazet
2013-07-09 13:53 ` Toke Høiland-Jørgensen
2013-07-09 14:07 ` Eric Dumazet
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=87zjtvvpap.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=eric.dumazet@gmail.com \
--cc=swmike@swm.pp.se \
/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