diff options
| author |   Vinicius Costa Gomes <vinicius.gomes@intel.com> | 2019-10-14 13:38:22 -0700 |
|---|---|---|
| committer |   David S. Miller <davem@davemloft.net> | 2019-10-15 20:32:04 -0700 |
| commit | 28aa7c86c2b49f659c8460a89e53b506c45979bb (patch) | |
| tree | ed91b53474128aef1288f49dda4a4ce8bf7e249a /net/sctp/socket.c | |
| parent | net: avoid potential infinite loop in tc_ctl_action() (diff) | |
| download | linux-dev-28aa7c86c2b49f659c8460a89e53b506c45979bb.tar.xz linux-dev-28aa7c86c2b49f659c8460a89e53b506c45979bb.zip | |
sched: etf: Fix ordering of packets with same txtime
When a application sends many packets with the same txtime, they may
be transmitted out of order (different from the order in which they
were enqueued).
This happens because when inserting elements into the tree, when the
txtime of two packets are the same, the new packet is inserted at the
left side of the tree, causing the reordering. The only effect of this
change should be that packets with the same txtime will be transmitted
in the order they are enqueued.
The application in question (the AVTP GStreamer plugin, still in
development) is sending video traffic, in which each video frame have
a single presentation time, the problem is that when packetizing,
multiple packets end up with the same txtime.
The receiving side was rejecting packets because they were being
received out of order.
Fixes: 25db26a91364 ("net/sched: Introduce the ETF Qdisc")
Reported-by: Ederson de Souza <ederson.desouza@intel.com>
Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions