Don't clone d6d packet
Summary: Sending a potentially over-sized d6d packet on PTO might be a bad idea. Plus, a PTO probe containing app data sounds more useful than only "empty" packet.
MODIFY
quic/api/QuicPacketScheduler.cpp
quic/api/QuicPacketScheduler.cpp
@@ -757,7 +757,8 @@ SchedulingResult CloningScheduler::scheduleFramesForPacket(
std::move(builder).releaseOutputBuffer();
// Look for an outstanding packet that's no larger than the writableBytes
for (auto& outstandingPacket : conn_.outstandings.packets) {
- if (outstandingPacket.declaredLost) {
+ if (outstandingPacket.declaredLost ||
+ outstandingPacket.metadata.isD6DProbe) {
continue;
}
auto opPnSpace = outstandingPacket.packet.header.getPacketNumberSpace();

Don't clone d6d packet

Summary: Sending a potentially over-sized d6d packet on PTO might be a bad idea. Plus, a PTO probe containing app data sounds more useful than only "empty" packet.

Reviewed By: yangchi

Differential Revision: D25109633

fbshipit-source-id: ded0c02397b7dc4c346f3aa9b61869836791baec