Increase maximum probing bitrate to 100Mbps.

Cap probing bitrate by the max bitrate instead of hardcoded 10Mbps.

Previously probing bitrate was capped at 10Mbps, which is too low for some
application. Now ProbeContoller limits max probing rate to max allowed
bitrate, which can be specified by the application.

BUG=webrtc:6332
Committed: https://crrev.com/07c147d25da77a1d966387c0f9257cfcda5b0a9f
Cr-Commit-Position: refs/heads/master@{#14927}

[Sergey Ulanov, 2016-10-19 23:55:16]

sergeyu@chromium.org changed reviewers:
+ stefan@webrtc.org

[Sergey Ulanov, 2016-10-24 17:29:02]

ping

[Sergey Ulanov, 2016-10-26 23:01:06]

Description was changed from

==========
Increase maximum probing bitrate to 100Mbps.

Previously probing bitrate was capped at 10Mbps, which seems too low.

BUG=webrtc:6332
==========

to

==========
Cap probing bitrate by the max bitrate instead of hardcoded 10Mbps.

Previously probing bitrate was capped at 10Mbps, which is too low for some 
application. Now ProbeContoller limits max probing rate to max allowed 
bitrate, which can be specified by the application.

BUG=webrtc:6332
==========

[stefan-webrtc, 2016-10-31 12:01:31]

lgtm

[Sergey Ulanov, 2016-10-31 17:50:55]

PTAL: I found that max_bitrate_bps is set to 0 when the application doesn't
specify max bitrate, as result probing would be effectively disabled in that
case. Update this CL to keep using 10Mbps limit for the case when the
application doesn't specify max bitrate.

[Sergey Ulanov, 2016-11-03 17:14:06]

The CQ bit was checked by sergeyu@chromium.org

[Sergey Ulanov, 2016-11-03 17:14:06]

The patchset sent to the CQ was uploaded after l-g-t-m from stefan@webrtc.org
Link to the patchset: https://codereview.webrtc.org/2430133005/#ps40001 (title:
"handle max_bitrate_bps = 0")

[commit-bot: I haz the power, 2016-11-03 17:14:08]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

[commit-bot: I haz the power, 2016-11-03 17:19:58]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-11-03 17:19:59]

Try jobs failed on following builders:
  linux_ubsan_vptr on master.tryserver.webrtc (JOB_FAILED,
http://build.chromium.org/p/tryserver.webrtc/builders/linux_ubsan_vptr/builds...)

[Sergey Ulanov, 2016-11-03 18:27:23]

The CQ bit was checked by sergeyu@chromium.org

[Sergey Ulanov, 2016-11-03 18:27:24]

The patchset sent to the CQ was uploaded after l-g-t-m from stefan@webrtc.org
Link to the patchset: https://codereview.webrtc.org/2430133005/#ps60001 (title:
"fix tests")

[commit-bot: I haz the power, 2016-11-03 18:27:33]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

[commit-bot: I haz the power, 2016-11-03 18:59:51]

Description was changed from

==========
Cap probing bitrate by the max bitrate instead of hardcoded 10Mbps.

Previously probing bitrate was capped at 10Mbps, which is too low for some 
application. Now ProbeContoller limits max probing rate to max allowed 
bitrate, which can be specified by the application.

BUG=webrtc:6332
==========

to

==========
Cap probing bitrate by the max bitrate instead of hardcoded 10Mbps.

Previously probing bitrate was capped at 10Mbps, which is too low for some 
application. Now ProbeContoller limits max probing rate to max allowed 
bitrate, which can be specified by the application.

BUG=webrtc:6332
==========

[commit-bot: I haz the power, 2016-11-03 18:59:52]

Committed patchset #4 (id:60001)

[commit-bot: I haz the power, 2016-11-03 19:14:33]

Description was changed from

==========
Cap probing bitrate by the max bitrate instead of hardcoded 10Mbps.

Previously probing bitrate was capped at 10Mbps, which is too low for some 
application. Now ProbeContoller limits max probing rate to max allowed 
bitrate, which can be specified by the application.

BUG=webrtc:6332
==========

to

==========
Cap probing bitrate by the max bitrate instead of hardcoded 10Mbps.

Previously probing bitrate was capped at 10Mbps, which is too low for some
application. Now ProbeContoller limits max probing rate to max allowed
bitrate, which can be specified by the application.

BUG=webrtc:6332

Committed: https://crrev.com/07c147d25da77a1d966387c0f9257cfcda5b0a9f
Cr-Commit-Position: refs/heads/master@{#14927}
==========

[commit-bot: I haz the power, 2016-11-03 19:14:34]

Patchset 4 (id:??) landed as
https://crrev.com/07c147d25da77a1d966387c0f9257cfcda5b0a9f
Cr-Commit-Position: refs/heads/master@{#14927}