Fixing issue that causes STUN throttle rate to be off by a factor of 1000.

Fixing issue that causes STUN throttle rate to be off by a factor of 1000.

The limit is supposed to be 256kbps, but it was actually effectively
256Mbps due to dividing a microsecond count by "microseconds per
millisecond" instead of "per second".

BUG=chromium:622323
NOTRY=true
NOPRESUBMIT=true

Review-Url: https://codereview.chromium.org/2398603004
Cr-Commit-Position: refs/heads/master@{#423902}
(cherry picked from commit e9e3f35d8eba2a4f0d88df274fc4eca48e811083)

[Taylor_Brandstetter, 2016-10-11 00:43:02]

deadbeef@chromium.org changed reviewers:
+ sergeyu@chromium.org

[Taylor_Brandstetter, 2016-10-11 00:43:03]

Hi Sergey; this is the same CL you reviewed earlier, being merged to M55. I'm
not a committer, so could you sign off on it? Thanks!

[Sergey Ulanov, 2016-10-11 17:28:48]

lgtm

[Sergey Ulanov, 2016-10-11 17:28:55]

The CQ bit was checked by sergeyu@chromium.org

[commit-bot: I haz the power, 2016-10-11 17:29:24]

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

[commit-bot: I haz the power, 2016-10-11 17:29:27]

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

[commit-bot: I haz the power, 2016-10-11 17:29:29]

CLs for remote refs other than refs/pending/heads/master must contain NOTRY=true
and NOPRESUBMIT=true in order for the CQ to process them

[Taylor_Brandstetter, 2016-10-11 17:31:54]

Description was changed from

==========
Fixing issue that causes STUN throttle rate to be off by a factor of 1000.

The limit is supposed to be 256kbps, but it was actually effectively
256Mbps due to dividing a microsecond count by "microseconds per
millisecond" instead of "per second".

BUG=chromium:622323

Review-Url: https://codereview.chromium.org/2398603004
Cr-Commit-Position: refs/heads/master@{#423902}
(cherry picked from commit e9e3f35d8eba2a4f0d88df274fc4eca48e811083)
==========

to

==========
Fixing issue that causes STUN throttle rate to be off by a factor of 1000.

The limit is supposed to be 256kbps, but it was actually effectively
256Mbps due to dividing a microsecond count by "microseconds per
millisecond" instead of "per second".

BUG=chromium:622323
NOTRY=true
NOPRESUBMIT=true

Review-Url: https://codereview.chromium.org/2398603004
Cr-Commit-Position: refs/heads/master@{#423902}
(cherry picked from commit e9e3f35d8eba2a4f0d88df274fc4eca48e811083)
==========

[Taylor_Brandstetter, 2016-10-11 17:31:59]

The CQ bit was checked by deadbeef@chromium.org

[commit-bot: I haz the power, 2016-10-11 17:32:34]

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

[commit-bot: I haz the power, 2016-10-11 17:39:11]

Description was changed from

==========
Fixing issue that causes STUN throttle rate to be off by a factor of 1000.

The limit is supposed to be 256kbps, but it was actually effectively
256Mbps due to dividing a microsecond count by "microseconds per
millisecond" instead of "per second".

BUG=chromium:622323
NOTRY=true
NOPRESUBMIT=true

Review-Url: https://codereview.chromium.org/2398603004
Cr-Commit-Position: refs/heads/master@{#423902}
(cherry picked from commit e9e3f35d8eba2a4f0d88df274fc4eca48e811083)
==========

to

==========
Fixing issue that causes STUN throttle rate to be off by a factor of 1000.

The limit is supposed to be 256kbps, but it was actually effectively
256Mbps due to dividing a microsecond count by "microseconds per
millisecond" instead of "per second".

BUG=chromium:622323
NOTRY=true
NOPRESUBMIT=true

Review-Url: https://codereview.chromium.org/2398603004
Cr-Commit-Position: refs/heads/master@{#423902}
(cherry picked from commit e9e3f35d8eba2a4f0d88df274fc4eca48e811083)
==========

[commit-bot: I haz the power, 2016-10-11 17:39:12]

Committed patchset #1 (id:1)