Propagate packet pacing information to SendTimeHistory.

webrtc/modules/rtp_rtcp/source/rtp_rtcp_impl.cc

Index: webrtc/modules/rtp_rtcp/source/rtp_rtcp_impl.cc
diff --git a/webrtc/modules/rtp_rtcp/source/rtp_rtcp_impl.cc b/webrtc/modules/rtp_rtcp/source/rtp_rtcp_impl.cc
index f1bee961cb97140b51fb9b3183a094a085f967cc..32109842b1bf0000cc633b8d1e47fa9555bd55d6 100644
--- a/webrtc/modules/rtp_rtcp/source/rtp_rtcp_impl.cc
+++ b/webrtc/modules/rtp_rtcp/source/rtp_rtcp_impl.cc
@@ -394,14 +394,13 @@ bool ModuleRtpRtcpImpl::TimeToSendPacket(uint32_t ssrc,
                                          bool retransmission,
                                          const PacedPacketInfo& pacing_info) {
   return rtp_sender_.TimeToSendPacket(ssrc, sequence_number, capture_time_ms,
-                                      retransmission,
-                                      pacing_info.probe_cluster_id);
+                                      retransmission, pacing_info);

[nisse-webrtc, 2017/02/22 12:37:47]

And this is where pacing_info gets passed further on.

Is it populated at this point? Are values used yet at the end of the line?

[philipel, 2017/02/22 13:11:26]

Yes, |pacing_info| is populated by the pacer and is not used until we actually
receive feedback. The |pacing_info| is just passed around everywhere just to end
up in SendTimeHistory.

 }
 
 size_t ModuleRtpRtcpImpl::TimeToSendPadding(
     size_t bytes,
     const PacedPacketInfo& pacing_info) {
-  return rtp_sender_.TimeToSendPadding(bytes, pacing_info.probe_cluster_id);
+  return rtp_sender_.TimeToSendPadding(bytes, pacing_info);
 }
 
 size_t ModuleRtpRtcpImpl::MaxPayloadSize() const {