netdev - Re: [PATCH 2/2] net: netem: always adjust now/delay when not reordering

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1377104417.4226.133.camel@edumazet-glaptop>
Date:	Wed, 21 Aug 2013 10:00:17 -0700
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Ferry Huberts <mailings@...ie.com>
Cc:	Johannes Naab <jn@...sta.de>, netdev@...r.kernel.org,
	hagen@...u.net
Subject: Re: [PATCH 2/2] net: netem: always adjust now/delay when not
 reordering

On Wed, 2013-08-21 at 18:14 +0200, Ferry Huberts wrote:

> Well no. We expected no reordering because reordering is not enabled.

Sending packets with random delays happening in the 'network' _will_
reorder packets at the receiver.

The 'reorder' netem attribute is quite limited and not practical,
because it only queues the packet at the head of the queue instead of
tail. This is not what happens on the networks.

You want something very special, and this needs a new parameter to netem
qdisc, or a new qdisc.

If I setup "netem rate 1Mbit delay 1000ms 50ms", and send a burst of 100
small packets, I expect these _all_ packets reach the destination in
less than 1050ms.

I do not want packet1 being delivered at t0+1020ms,
packet2 being delivered at t0+1020+1030ms
packet100 being delivered at t0+1020+1030++...+ = t0+~100sec

If your patch solves the problem, good, but I see no clear test of this.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html