Landing Recent QUIC changes until 03:18 AM, May 28, UTC

Landing Recent QUIC changes until 03:18 AM, May 28, UTC

Flags updated.
https://codereview.chromium.org/2920713002/

Default to BBR congestion control for QUIC. Protected by
FLAGS_quic_reloadable_flag_quic_default_to_bbr.

Merge internal change: 157287886
https://codereview.chromium.org/2917823004/


Remove is_deletable_ from QuicStream. Add QuicStream::IsWaitingForAcks which returns true if stream is waiting for acks.

Merge internal change: 157256038
https://codereview.chromium.org/2916233002/


Remove QuicPacketNumberQueue::Complement() because it is no longer
used and will add work to the process of changing over to a deque from
an IntervalSet.

n/a (Test only)

Merge internal change: 157226948
https://codereview.chromium.org/2919733002/


Groundwork for cancelling quartc streams after a deadline is exceeded.

In the quic/quartc wrapper:
- Adds a method to QuartcSessionInterface to cancel a stream by number
- Fixes stream error code reporting
- Fixes spurious reset frames sent with QUIC_RST_STREAM_ACKNOWLEDGEMENT

This is done by number on QuartcSessionInterface instead of by a
method on a stream (or by passing the session a pointer to the stream)
because the quartc session owns quartc streams and may delete them
before the deadline.  Under the covers, the CancelStream method resets
a stream with error code 6 (QUIC_STREAM_CANCELLED).

QuartcStream currently only reports a non-zero error code if there's a
connection error.  This cl rectifies that by exposing both
stream_error() and connection_error() and letting callers examine
whichever one they want.

Since Quartc only sends on outgoing streams, it never sent a fin on
incoming streams.  This led to it not closing incoming streams
cleanly.  Whenever it closed an incoming stream, it sent a reset frame
with the error code QUIC_RST_STREAM_ACKNOWLEDGEMENT, in order to
communicate a final byte offset.  This isn't necessary, since we never
send anything (the final offset is always 0).  Instead, we now close
the reverse direction (sending on inbound streams, receiving on
outbound streams) immediately on stream creation, by simulating a fin.
This prevents spurious reset frames that look like errors.

In quartc:
- Adds CancelStream to the thread-safe wrapper
- Adds an optional parameter to SendOutgoingFrame to set a deadline
- Fixes incorrectly ordered boolean parameters in the
quartc_connection_test

SendOutgoingFrame will now schedule a task to cancel a stream if it is
given a non-infinite deadline.  The new deadline parameter defaults to
infinite to preserve current behavior.  We'll likely only use this for
video and audio streams, not for data and control streams.

n/a (only linked by quartc)
Merge internal change: 157132817


https://codereview.chromium.org/2913413002/
n/a (test-only change)

Merge internal change: 156881271
https://codereview.chromium.org/2913153003/


Inline methods of QuicBandwidth class.  No functional change; not
flag-protected.

Since "B" in "BBR" stands for bandwidth, we've been using
QuicBandwidth class much more actively on the hot paths.  The overhead
from calling QuicBandwidth methods started to show up on profiles, so
I've maked a CL to make them all inlined, as it was done with
QuicTime::Delta.

This removes the non-negativity check from the QuicBandwidth
constructor where it would previously result in a QUIC_BUG, since it's
now constexpr.

Merge internal change: 156806926
https://codereview.chromium.org/2921603002/


This QUIC change includes: 1) Change QuicStream's life
time. QuicStream is not deletable when it has unacked data (including
FIN). 2) Closed but not deletable QuicStream is moved to
zombie_streams in QuicSession. 3) Move ack listener to QuicStream. 4)
QuicHeaderStream keeps track of unacked headers which have not null
ack listener. 5) Both QuicStream and QuicSession implement
StreamNotifier which will be notified when stream frame is acked or
retransmitted.

Protected by FLAGS_quic_reloadable_flag_quic_use_stream_notifier.

Merge internal change: 156886444
https://codereview.chromium.org/2915873003/


Move tests from portable_quic to the new quic/quartc wrapper location.
n/a (test only, tests code that is only linked by Quartc)

Merge internal change: 156794055
https://codereview.chromium.org/2915993002/


Use BBR for Quartc congestion control.

We think BBR will do what we want in Quartc: generally avoid queuing
packets in the network and keep RTT low.  WebRTC does something
similar with its own bandwidth estimator.

We're starting work to optimize media flow, and we don't want to waste
effort optimizing on top of the wrong congestion control algorithm.
n/a (only linked by quartc)

Merge internal change: 156746324
https://codereview.chromium.org/2912393003/

BUG=

Review-Url: https://codereview.chromium.org/2916033003
Cr-Commit-Position: refs/heads/master@{#476570}
Committed: https://chromium.googlesource.com/chromium/src/+/3c1d5ca822a369a0ef65d7044100f73903fdbdc0

[Jana, 2017-06-01 07:12:22]

Description was changed from

==========
Flags updated.
https://codereview.chromium.org/2920713002/

Default to BBR congestion control for QUIC. Protected by
FLAGS_quic_reloadable_flag_quic_default_to_bbr.

Merge internal change: 157287886
https://codereview.chromium.org/2917823004/


Remove QuicPacketNumberQueue::Complement() because it is no longer
used and will add work to the process of changing over to a deque from
an IntervalSet.

n/a (Test only)

Merge internal change: 157226948
https://codereview.chromium.org/2919733002/


Groundwork for cancelling quartc streams after a deadline is exceeded.

In the quic/quartc wrapper:
- Adds a method to QuartcSessionInterface to cancel a stream by number
- Fixes stream error code reporting
- Fixes spurious reset frames sent with QUIC_RST_STREAM_ACKNOWLEDGEMENT

This is done by number on QuartcSessionInterface instead of by a
method on a stream (or by passing the session a pointer to the stream)
because the quartc session owns quartc streams and may delete them
before the deadline.  Under the covers, the CancelStream method resets
a stream with error code 6 (QUIC_STREAM_CANCELLED).

QuartcStream currently only reports a non-zero error code if there's a
connection error.  This cl rectifies that by exposing both
stream_error() and connection_error() and letting callers examine
whichever one they want.

Since Quartc only sends on outgoing streams, it never sent a fin on
incoming streams.  This led to it not closing incoming streams
cleanly.  Whenever it closed an incoming stream, it sent a reset frame
with the error code QUIC_RST_STREAM_ACKNOWLEDGEMENT, in order to
communicate a final byte offset.  This isn't necessary, since we never
send anything (the final offset is always 0).  Instead, we now close
the reverse direction (sending on inbound streams, receiving on
outbound streams) immediately on stream creation, by simulating a fin.
This prevents spurious reset frames that look like errors.

In quartc:
- Adds CancelStream to the thread-safe wrapper
- Adds an optional parameter to SendOutgoingFrame to set a deadline
- Fixes incorrectly ordered boolean parameters in the
quartc_connection_test

SendOutgoingFrame will now schedule a task to cancel a stream if it is
given a non-infinite deadline.  The new deadline parameter defaults to
infinite to preserve current behavior.  We'll likely only use this for
video and audio streams, not for data and control streams.

n/a (only linked by quartc)
Merge internal change: 157132817


https://codereview.chromium.org/2913413002/
n/a (test-only change)

Merge internal change: 156881271
https://codereview.chromium.org/2913153003/


Inline methods of QuicBandwidth class.  No functional change; not
flag-protected.

Since "B" in "BBR" stands for bandwidth, we've been using
QuicBandwidth class much more actively on the hot paths.  The overhead
from calling QuicBandwidth methods started to show up on profiles, so
I've maked a CL to make them all inlined, as it was done with
QuicTime::Delta.

This removes the non-negativity check from the QuicBandwidth
constructor where it would previously result in a QUIC_BUG, since it's
now constexpr.

Merge internal change: 156806926
https://codereview.chromium.org/2921603002/


This QUIC change includes: 1) Change QuicStream's life
time. QuicStream is not deletable when it has unacked data (including
FIN). 2) Closed but not deletable QuicStream is moved to
zombie_streams in QuicSession. 3) Move ack listener to QuicStream. 4)
QuicHeaderStream keeps track of unacked headers which have not null
ack listener. 5) Both QuicStream and QuicSession implement
StreamNotifier which will be notified when stream frame is acked or
retransmitted.

Protected by FLAGS_quic_reloadable_flag_quic_use_stream_notifier.

Merge internal change: 156886444
https://codereview.chromium.org/2915873003/


Move tests from portable_quic to the new quic/quartc wrapper location.
n/a (test only, tests code that is only linked by Quartc)

Merge internal change: 156794055
https://codereview.chromium.org/2915993002/


Use BBR for Quartc congestion control.

We think BBR will do what we want in Quartc: generally avoid queuing
packets in the network and keep RTT low.  WebRTC does something
similar with its own bandwidth estimator.

We're starting work to optimize media flow, and we don't want to waste
effort optimizing on top of the wrong congestion control algorithm.
n/a (only linked by quartc)

Merge internal change: 156746324
https://codereview.chromium.org/2912393003/

BUG=
==========

to

==========
Flags updated.
https://codereview.chromium.org/2920713002/

Default to BBR congestion control for QUIC. Protected by
FLAGS_quic_reloadable_flag_quic_default_to_bbr.

Merge internal change: 157287886
https://codereview.chromium.org/2917823004/


Remove QuicPacketNumberQueue::Complement() because it is no longer
used and will add work to the process of changing over to a deque from
an IntervalSet.

n/a (Test only)

Merge internal change: 157226948
https://codereview.chromium.org/2919733002/


Groundwork for cancelling quartc streams after a deadline is exceeded.

In the quic/quartc wrapper:
- Adds a method to QuartcSessionInterface to cancel a stream by number
- Fixes stream error code reporting
- Fixes spurious reset frames sent with QUIC_RST_STREAM_ACKNOWLEDGEMENT

This is done by number on QuartcSessionInterface instead of by a
method on a stream (or by passing the session a pointer to the stream)
because the quartc session owns quartc streams and may delete them
before the deadline.  Under the covers, the CancelStream method resets
a stream with error code 6 (QUIC_STREAM_CANCELLED).

QuartcStream currently only reports a non-zero error code if there's a
connection error.  This cl rectifies that by exposing both
stream_error() and connection_error() and letting callers examine
whichever one they want.

Since Quartc only sends on outgoing streams, it never sent a fin on
incoming streams.  This led to it not closing incoming streams
cleanly.  Whenever it closed an incoming stream, it sent a reset frame
with the error code QUIC_RST_STREAM_ACKNOWLEDGEMENT, in order to
communicate a final byte offset.  This isn't necessary, since we never
send anything (the final offset is always 0).  Instead, we now close
the reverse direction (sending on inbound streams, receiving on
outbound streams) immediately on stream creation, by simulating a fin.
This prevents spurious reset frames that look like errors.

In quartc:
- Adds CancelStream to the thread-safe wrapper
- Adds an optional parameter to SendOutgoingFrame to set a deadline
- Fixes incorrectly ordered boolean parameters in the
quartc_connection_test

SendOutgoingFrame will now schedule a task to cancel a stream if it is
given a non-infinite deadline.  The new deadline parameter defaults to
infinite to preserve current behavior.  We'll likely only use this for
video and audio streams, not for data and control streams.

n/a (only linked by quartc)
Merge internal change: 157132817


https://codereview.chromium.org/2913413002/
n/a (test-only change)

Merge internal change: 156881271
https://codereview.chromium.org/2913153003/


Inline methods of QuicBandwidth class.  No functional change; not
flag-protected.

Since "B" in "BBR" stands for bandwidth, we've been using
QuicBandwidth class much more actively on the hot paths.  The overhead
from calling QuicBandwidth methods started to show up on profiles, so
I've maked a CL to make them all inlined, as it was done with
QuicTime::Delta.

This removes the non-negativity check from the QuicBandwidth
constructor where it would previously result in a QUIC_BUG, since it's
now constexpr.

Merge internal change: 156806926
https://codereview.chromium.org/2921603002/


This QUIC change includes: 1) Change QuicStream's life
time. QuicStream is not deletable when it has unacked data (including
FIN). 2) Closed but not deletable QuicStream is moved to
zombie_streams in QuicSession. 3) Move ack listener to QuicStream. 4)
QuicHeaderStream keeps track of unacked headers which have not null
ack listener. 5) Both QuicStream and QuicSession implement
StreamNotifier which will be notified when stream frame is acked or
retransmitted.

Protected by FLAGS_quic_reloadable_flag_quic_use_stream_notifier.

Merge internal change: 156886444
https://codereview.chromium.org/2915873003/


Move tests from portable_quic to the new quic/quartc wrapper location.
n/a (test only, tests code that is only linked by Quartc)

Merge internal change: 156794055
https://codereview.chromium.org/2915993002/


Use BBR for Quartc congestion control.

We think BBR will do what we want in Quartc: generally avoid queuing
packets in the network and keep RTT low.  WebRTC does something
similar with its own bandwidth estimator.

We're starting work to optimize media flow, and we don't want to waste
effort optimizing on top of the wrong congestion control algorithm.
n/a (only linked by quartc)

Merge internal change: 156746324
https://codereview.chromium.org/2912393003/

BUG=
==========

[Jana, 2017-06-01 07:12:43]

Description was changed from

==========
Flags updated.
https://codereview.chromium.org/2920713002/

Default to BBR congestion control for QUIC. Protected by
FLAGS_quic_reloadable_flag_quic_default_to_bbr.

Merge internal change: 157287886
https://codereview.chromium.org/2917823004/


Remove QuicPacketNumberQueue::Complement() because it is no longer
used and will add work to the process of changing over to a deque from
an IntervalSet.

n/a (Test only)

Merge internal change: 157226948
https://codereview.chromium.org/2919733002/


Groundwork for cancelling quartc streams after a deadline is exceeded.

In the quic/quartc wrapper:
- Adds a method to QuartcSessionInterface to cancel a stream by number
- Fixes stream error code reporting
- Fixes spurious reset frames sent with QUIC_RST_STREAM_ACKNOWLEDGEMENT

This is done by number on QuartcSessionInterface instead of by a
method on a stream (or by passing the session a pointer to the stream)
because the quartc session owns quartc streams and may delete them
before the deadline.  Under the covers, the CancelStream method resets
a stream with error code 6 (QUIC_STREAM_CANCELLED).

QuartcStream currently only reports a non-zero error code if there's a
connection error.  This cl rectifies that by exposing both
stream_error() and connection_error() and letting callers examine
whichever one they want.

Since Quartc only sends on outgoing streams, it never sent a fin on
incoming streams.  This led to it not closing incoming streams
cleanly.  Whenever it closed an incoming stream, it sent a reset frame
with the error code QUIC_RST_STREAM_ACKNOWLEDGEMENT, in order to
communicate a final byte offset.  This isn't necessary, since we never
send anything (the final offset is always 0).  Instead, we now close
the reverse direction (sending on inbound streams, receiving on
outbound streams) immediately on stream creation, by simulating a fin.
This prevents spurious reset frames that look like errors.

In quartc:
- Adds CancelStream to the thread-safe wrapper
- Adds an optional parameter to SendOutgoingFrame to set a deadline
- Fixes incorrectly ordered boolean parameters in the
quartc_connection_test

SendOutgoingFrame will now schedule a task to cancel a stream if it is
given a non-infinite deadline.  The new deadline parameter defaults to
infinite to preserve current behavior.  We'll likely only use this for
video and audio streams, not for data and control streams.

n/a (only linked by quartc)
Merge internal change: 157132817


https://codereview.chromium.org/2913413002/
n/a (test-only change)

Merge internal change: 156881271
https://codereview.chromium.org/2913153003/


Inline methods of QuicBandwidth class.  No functional change; not
flag-protected.

Since "B" in "BBR" stands for bandwidth, we've been using
QuicBandwidth class much more actively on the hot paths.  The overhead
from calling QuicBandwidth methods started to show up on profiles, so
I've maked a CL to make them all inlined, as it was done with
QuicTime::Delta.

This removes the non-negativity check from the QuicBandwidth
constructor where it would previously result in a QUIC_BUG, since it's
now constexpr.

Merge internal change: 156806926
https://codereview.chromium.org/2921603002/


This QUIC change includes: 1) Change QuicStream's life
time. QuicStream is not deletable when it has unacked data (including
FIN). 2) Closed but not deletable QuicStream is moved to
zombie_streams in QuicSession. 3) Move ack listener to QuicStream. 4)
QuicHeaderStream keeps track of unacked headers which have not null
ack listener. 5) Both QuicStream and QuicSession implement
StreamNotifier which will be notified when stream frame is acked or
retransmitted.

Protected by FLAGS_quic_reloadable_flag_quic_use_stream_notifier.

Merge internal change: 156886444
https://codereview.chromium.org/2915873003/


Move tests from portable_quic to the new quic/quartc wrapper location.
n/a (test only, tests code that is only linked by Quartc)

Merge internal change: 156794055
https://codereview.chromium.org/2915993002/


Use BBR for Quartc congestion control.

We think BBR will do what we want in Quartc: generally avoid queuing
packets in the network and keep RTT low.  WebRTC does something
similar with its own bandwidth estimator.

We're starting work to optimize media flow, and we don't want to waste
effort optimizing on top of the wrong congestion control algorithm.
n/a (only linked by quartc)

Merge internal change: 156746324
https://codereview.chromium.org/2912393003/

BUG=
==========

to

==========
Landing Recent QUIC changes until 03:18 AM, May 28, UTC

Flags updated.
https://codereview.chromium.org/2920713002/

Default to BBR congestion control for QUIC. Protected by
FLAGS_quic_reloadable_flag_quic_default_to_bbr.

Merge internal change: 157287886
https://codereview.chromium.org/2917823004/


Remove QuicPacketNumberQueue::Complement() because it is no longer
used and will add work to the process of changing over to a deque from
an IntervalSet.

n/a (Test only)

Merge internal change: 157226948
https://codereview.chromium.org/2919733002/


Groundwork for cancelling quartc streams after a deadline is exceeded.

In the quic/quartc wrapper:
- Adds a method to QuartcSessionInterface to cancel a stream by number
- Fixes stream error code reporting
- Fixes spurious reset frames sent with QUIC_RST_STREAM_ACKNOWLEDGEMENT

This is done by number on QuartcSessionInterface instead of by a
method on a stream (or by passing the session a pointer to the stream)
because the quartc session owns quartc streams and may delete them
before the deadline.  Under the covers, the CancelStream method resets
a stream with error code 6 (QUIC_STREAM_CANCELLED).

QuartcStream currently only reports a non-zero error code if there's a
connection error.  This cl rectifies that by exposing both
stream_error() and connection_error() and letting callers examine
whichever one they want.

Since Quartc only sends on outgoing streams, it never sent a fin on
incoming streams.  This led to it not closing incoming streams
cleanly.  Whenever it closed an incoming stream, it sent a reset frame
with the error code QUIC_RST_STREAM_ACKNOWLEDGEMENT, in order to
communicate a final byte offset.  This isn't necessary, since we never
send anything (the final offset is always 0).  Instead, we now close
the reverse direction (sending on inbound streams, receiving on
outbound streams) immediately on stream creation, by simulating a fin.
This prevents spurious reset frames that look like errors.

In quartc:
- Adds CancelStream to the thread-safe wrapper
- Adds an optional parameter to SendOutgoingFrame to set a deadline
- Fixes incorrectly ordered boolean parameters in the
quartc_connection_test

SendOutgoingFrame will now schedule a task to cancel a stream if it is
given a non-infinite deadline.  The new deadline parameter defaults to
infinite to preserve current behavior.  We'll likely only use this for
video and audio streams, not for data and control streams.

n/a (only linked by quartc)
Merge internal change: 157132817


https://codereview.chromium.org/2913413002/
n/a (test-only change)

Merge internal change: 156881271
https://codereview.chromium.org/2913153003/


Inline methods of QuicBandwidth class.  No functional change; not
flag-protected.

Since "B" in "BBR" stands for bandwidth, we've been using
QuicBandwidth class much more actively on the hot paths.  The overhead
from calling QuicBandwidth methods started to show up on profiles, so
I've maked a CL to make them all inlined, as it was done with
QuicTime::Delta.

This removes the non-negativity check from the QuicBandwidth
constructor where it would previously result in a QUIC_BUG, since it's
now constexpr.

Merge internal change: 156806926
https://codereview.chromium.org/2921603002/


This QUIC change includes: 1) Change QuicStream's life
time. QuicStream is not deletable when it has unacked data (including
FIN). 2) Closed but not deletable QuicStream is moved to
zombie_streams in QuicSession. 3) Move ack listener to QuicStream. 4)
QuicHeaderStream keeps track of unacked headers which have not null
ack listener. 5) Both QuicStream and QuicSession implement
StreamNotifier which will be notified when stream frame is acked or
retransmitted.

Protected by FLAGS_quic_reloadable_flag_quic_use_stream_notifier.

Merge internal change: 156886444
https://codereview.chromium.org/2915873003/


Move tests from portable_quic to the new quic/quartc wrapper location.
n/a (test only, tests code that is only linked by Quartc)

Merge internal change: 156794055
https://codereview.chromium.org/2915993002/


Use BBR for Quartc congestion control.

We think BBR will do what we want in Quartc: generally avoid queuing
packets in the network and keep RTT low.  WebRTC does something
similar with its own bandwidth estimator.

We're starting work to optimize media flow, and we don't want to waste
effort optimizing on top of the wrong congestion control algorithm.
n/a (only linked by quartc)

Merge internal change: 156746324
https://codereview.chromium.org/2912393003/

BUG=
==========

[Jana, 2017-06-01 07:13:25]

The CQ bit was checked by jri@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-06-01 07:13:38]

Dry run: CQ is trying da patch.

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

[Jana, 2017-06-01 07:14:08]

jri@chromium.org changed reviewers:
+ rch@chromium.org

[commit-bot: I haz the power, 2017-06-01 07:24:15]

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

[commit-bot: I haz the power, 2017-06-01 07:24:16]

Dry run: Try jobs failed on following builders:
  ios-device on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)
  ios-device-xcode-clang on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device-xcode-...)
  mac_chromium_compile_dbg_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[Jana, 2017-06-02 00:06:06]

Description was changed from

==========
Landing Recent QUIC changes until 03:18 AM, May 28, UTC

Flags updated.
https://codereview.chromium.org/2920713002/

Default to BBR congestion control for QUIC. Protected by
FLAGS_quic_reloadable_flag_quic_default_to_bbr.

Merge internal change: 157287886
https://codereview.chromium.org/2917823004/


Remove QuicPacketNumberQueue::Complement() because it is no longer
used and will add work to the process of changing over to a deque from
an IntervalSet.

n/a (Test only)

Merge internal change: 157226948
https://codereview.chromium.org/2919733002/


Groundwork for cancelling quartc streams after a deadline is exceeded.

In the quic/quartc wrapper:
- Adds a method to QuartcSessionInterface to cancel a stream by number
- Fixes stream error code reporting
- Fixes spurious reset frames sent with QUIC_RST_STREAM_ACKNOWLEDGEMENT

This is done by number on QuartcSessionInterface instead of by a
method on a stream (or by passing the session a pointer to the stream)
because the quartc session owns quartc streams and may delete them
before the deadline.  Under the covers, the CancelStream method resets
a stream with error code 6 (QUIC_STREAM_CANCELLED).

QuartcStream currently only reports a non-zero error code if there's a
connection error.  This cl rectifies that by exposing both
stream_error() and connection_error() and letting callers examine
whichever one they want.

Since Quartc only sends on outgoing streams, it never sent a fin on
incoming streams.  This led to it not closing incoming streams
cleanly.  Whenever it closed an incoming stream, it sent a reset frame
with the error code QUIC_RST_STREAM_ACKNOWLEDGEMENT, in order to
communicate a final byte offset.  This isn't necessary, since we never
send anything (the final offset is always 0).  Instead, we now close
the reverse direction (sending on inbound streams, receiving on
outbound streams) immediately on stream creation, by simulating a fin.
This prevents spurious reset frames that look like errors.

In quartc:
- Adds CancelStream to the thread-safe wrapper
- Adds an optional parameter to SendOutgoingFrame to set a deadline
- Fixes incorrectly ordered boolean parameters in the
quartc_connection_test

SendOutgoingFrame will now schedule a task to cancel a stream if it is
given a non-infinite deadline.  The new deadline parameter defaults to
infinite to preserve current behavior.  We'll likely only use this for
video and audio streams, not for data and control streams.

n/a (only linked by quartc)
Merge internal change: 157132817


https://codereview.chromium.org/2913413002/
n/a (test-only change)

Merge internal change: 156881271
https://codereview.chromium.org/2913153003/


Inline methods of QuicBandwidth class.  No functional change; not
flag-protected.

Since "B" in "BBR" stands for bandwidth, we've been using
QuicBandwidth class much more actively on the hot paths.  The overhead
from calling QuicBandwidth methods started to show up on profiles, so
I've maked a CL to make them all inlined, as it was done with
QuicTime::Delta.

This removes the non-negativity check from the QuicBandwidth
constructor where it would previously result in a QUIC_BUG, since it's
now constexpr.

Merge internal change: 156806926
https://codereview.chromium.org/2921603002/


This QUIC change includes: 1) Change QuicStream's life
time. QuicStream is not deletable when it has unacked data (including
FIN). 2) Closed but not deletable QuicStream is moved to
zombie_streams in QuicSession. 3) Move ack listener to QuicStream. 4)
QuicHeaderStream keeps track of unacked headers which have not null
ack listener. 5) Both QuicStream and QuicSession implement
StreamNotifier which will be notified when stream frame is acked or
retransmitted.

Protected by FLAGS_quic_reloadable_flag_quic_use_stream_notifier.

Merge internal change: 156886444
https://codereview.chromium.org/2915873003/


Move tests from portable_quic to the new quic/quartc wrapper location.
n/a (test only, tests code that is only linked by Quartc)

Merge internal change: 156794055
https://codereview.chromium.org/2915993002/


Use BBR for Quartc congestion control.

We think BBR will do what we want in Quartc: generally avoid queuing
packets in the network and keep RTT low.  WebRTC does something
similar with its own bandwidth estimator.

We're starting work to optimize media flow, and we don't want to waste
effort optimizing on top of the wrong congestion control algorithm.
n/a (only linked by quartc)

Merge internal change: 156746324
https://codereview.chromium.org/2912393003/

BUG=
==========

to

==========
Landing Recent QUIC changes until 03:18 AM, May 28, UTC

Flags updated.
https://codereview.chromium.org/2920713002/

Default to BBR congestion control for QUIC. Protected by
FLAGS_quic_reloadable_flag_quic_default_to_bbr.

Merge internal change: 157287886
https://codereview.chromium.org/2917823004/


Remove is_deletable_ from QuicStream. Add QuicStream::IsWaitingForAcks which
returns true if stream is waiting for acks.

Merge internal change: 157256038
https://codereview.chromium.org/2916233002/


Remove QuicPacketNumberQueue::Complement() because it is no longer
used and will add work to the process of changing over to a deque from
an IntervalSet.

n/a (Test only)

Merge internal change: 157226948
https://codereview.chromium.org/2919733002/


Groundwork for cancelling quartc streams after a deadline is exceeded.

In the quic/quartc wrapper:
- Adds a method to QuartcSessionInterface to cancel a stream by number
- Fixes stream error code reporting
- Fixes spurious reset frames sent with QUIC_RST_STREAM_ACKNOWLEDGEMENT

This is done by number on QuartcSessionInterface instead of by a
method on a stream (or by passing the session a pointer to the stream)
because the quartc session owns quartc streams and may delete them
before the deadline.  Under the covers, the CancelStream method resets
a stream with error code 6 (QUIC_STREAM_CANCELLED).

QuartcStream currently only reports a non-zero error code if there's a
connection error.  This cl rectifies that by exposing both
stream_error() and connection_error() and letting callers examine
whichever one they want.

Since Quartc only sends on outgoing streams, it never sent a fin on
incoming streams.  This led to it not closing incoming streams
cleanly.  Whenever it closed an incoming stream, it sent a reset frame
with the error code QUIC_RST_STREAM_ACKNOWLEDGEMENT, in order to
communicate a final byte offset.  This isn't necessary, since we never
send anything (the final offset is always 0).  Instead, we now close
the reverse direction (sending on inbound streams, receiving on
outbound streams) immediately on stream creation, by simulating a fin.
This prevents spurious reset frames that look like errors.

In quartc:
- Adds CancelStream to the thread-safe wrapper
- Adds an optional parameter to SendOutgoingFrame to set a deadline
- Fixes incorrectly ordered boolean parameters in the
quartc_connection_test

SendOutgoingFrame will now schedule a task to cancel a stream if it is
given a non-infinite deadline.  The new deadline parameter defaults to
infinite to preserve current behavior.  We'll likely only use this for
video and audio streams, not for data and control streams.

n/a (only linked by quartc)
Merge internal change: 157132817


https://codereview.chromium.org/2913413002/
n/a (test-only change)

Merge internal change: 156881271
https://codereview.chromium.org/2913153003/


Inline methods of QuicBandwidth class.  No functional change; not
flag-protected.

Since "B" in "BBR" stands for bandwidth, we've been using
QuicBandwidth class much more actively on the hot paths.  The overhead
from calling QuicBandwidth methods started to show up on profiles, so
I've maked a CL to make them all inlined, as it was done with
QuicTime::Delta.

This removes the non-negativity check from the QuicBandwidth
constructor where it would previously result in a QUIC_BUG, since it's
now constexpr.

Merge internal change: 156806926
https://codereview.chromium.org/2921603002/


This QUIC change includes: 1) Change QuicStream's life
time. QuicStream is not deletable when it has unacked data (including
FIN). 2) Closed but not deletable QuicStream is moved to
zombie_streams in QuicSession. 3) Move ack listener to QuicStream. 4)
QuicHeaderStream keeps track of unacked headers which have not null
ack listener. 5) Both QuicStream and QuicSession implement
StreamNotifier which will be notified when stream frame is acked or
retransmitted.

Protected by FLAGS_quic_reloadable_flag_quic_use_stream_notifier.

Merge internal change: 156886444
https://codereview.chromium.org/2915873003/


Move tests from portable_quic to the new quic/quartc wrapper location.
n/a (test only, tests code that is only linked by Quartc)

Merge internal change: 156794055
https://codereview.chromium.org/2915993002/


Use BBR for Quartc congestion control.

We think BBR will do what we want in Quartc: generally avoid queuing
packets in the network and keep RTT low.  WebRTC does something
similar with its own bandwidth estimator.

We're starting work to optimize media flow, and we don't want to waste
effort optimizing on top of the wrong congestion control algorithm.
n/a (only linked by quartc)

Merge internal change: 156746324
https://codereview.chromium.org/2912393003/

BUG=
==========

[Jana, 2017-06-02 00:13:48]

The CQ bit was checked by jri@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-06-02 00:15:01]

Dry run: 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, 2017-06-02 00:15:03]

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

[commit-bot: I haz the power, 2017-06-02 00:15:04]

Dry run: CQ cannot get SignCLA result. Please try later.

[Ryan Hamilton, 2017-06-02 00:19:18]

lgtm

https://codereview.chromium.org/2916033003/diff/20001/net/quic/quartc/quartc_...
File net/quic/quartc/quartc_stream.h (right):

https://codereview.chromium.org/2916033003/diff/20001/net/quic/quartc/quartc_...
net/quic/quartc/quartc_stream.h:15: class QUIC_EXPORT_PRIVATE QuartcStream :
public QuicStream,
Please make sure these get merged back, as well.

[Jana, 2017-06-02 00:36:19]

The CQ bit was checked by jri@chromium.org

[commit-bot: I haz the power, 2017-06-02 00:37:12]

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, 2017-06-02 01:28:08]

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

[commit-bot: I haz the power, 2017-06-02 01:28:09]

Try jobs failed on following builders:
  ios-simulator on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...)

[Jana, 2017-06-02 01:32:46]

The CQ bit was checked by jri@chromium.org

[Jana, 2017-06-02 01:32:47]

The patchset sent to the CQ was uploaded after l-g-t-m from rch@chromium.org
Link to the patchset: https://codereview.chromium.org/2916033003/#ps60001
(title: "Maybe missed a QUIC_EXPORT_PRIVATE")

[commit-bot: I haz the power, 2017-06-02 01:33:28]

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, 2017-06-02 02:58:22]

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

[commit-bot: I haz the power, 2017-06-02 02:58:24]

Try jobs failed on following builders:
  win_chromium_compile_dbg_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_comp...)

[Jana, 2017-06-02 03:04:42]

The CQ bit was checked by jri@chromium.org

[Jana, 2017-06-02 03:04:43]

The patchset sent to the CQ was uploaded after l-g-t-m from rch@chromium.org
Link to the patchset: https://codereview.chromium.org/2916033003/#ps80001
(title: "A few more EXPORTs.")

[commit-bot: I haz the power, 2017-06-02 03:05:16]

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, 2017-06-02 04:52:26]

CQ is committing da patch.

Bot data: {"patchset_id": 80001, "attempt_start_ts": 1496372682661000,
"parent_rev": "7073ae5bc6af913c649500e015210992f9c7111a", "commit_rev":
"3c1d5ca822a369a0ef65d7044100f73903fdbdc0"}

[commit-bot: I haz the power, 2017-06-02 04:52:35]

Description was changed from

==========
Landing Recent QUIC changes until 03:18 AM, May 28, UTC

Flags updated.
https://codereview.chromium.org/2920713002/

Default to BBR congestion control for QUIC. Protected by
FLAGS_quic_reloadable_flag_quic_default_to_bbr.

Merge internal change: 157287886
https://codereview.chromium.org/2917823004/


Remove is_deletable_ from QuicStream. Add QuicStream::IsWaitingForAcks which
returns true if stream is waiting for acks.

Merge internal change: 157256038
https://codereview.chromium.org/2916233002/


Remove QuicPacketNumberQueue::Complement() because it is no longer
used and will add work to the process of changing over to a deque from
an IntervalSet.

n/a (Test only)

Merge internal change: 157226948
https://codereview.chromium.org/2919733002/


Groundwork for cancelling quartc streams after a deadline is exceeded.

In the quic/quartc wrapper:
- Adds a method to QuartcSessionInterface to cancel a stream by number
- Fixes stream error code reporting
- Fixes spurious reset frames sent with QUIC_RST_STREAM_ACKNOWLEDGEMENT

This is done by number on QuartcSessionInterface instead of by a
method on a stream (or by passing the session a pointer to the stream)
because the quartc session owns quartc streams and may delete them
before the deadline.  Under the covers, the CancelStream method resets
a stream with error code 6 (QUIC_STREAM_CANCELLED).

QuartcStream currently only reports a non-zero error code if there's a
connection error.  This cl rectifies that by exposing both
stream_error() and connection_error() and letting callers examine
whichever one they want.

Since Quartc only sends on outgoing streams, it never sent a fin on
incoming streams.  This led to it not closing incoming streams
cleanly.  Whenever it closed an incoming stream, it sent a reset frame
with the error code QUIC_RST_STREAM_ACKNOWLEDGEMENT, in order to
communicate a final byte offset.  This isn't necessary, since we never
send anything (the final offset is always 0).  Instead, we now close
the reverse direction (sending on inbound streams, receiving on
outbound streams) immediately on stream creation, by simulating a fin.
This prevents spurious reset frames that look like errors.

In quartc:
- Adds CancelStream to the thread-safe wrapper
- Adds an optional parameter to SendOutgoingFrame to set a deadline
- Fixes incorrectly ordered boolean parameters in the
quartc_connection_test

SendOutgoingFrame will now schedule a task to cancel a stream if it is
given a non-infinite deadline.  The new deadline parameter defaults to
infinite to preserve current behavior.  We'll likely only use this for
video and audio streams, not for data and control streams.

n/a (only linked by quartc)
Merge internal change: 157132817


https://codereview.chromium.org/2913413002/
n/a (test-only change)

Merge internal change: 156881271
https://codereview.chromium.org/2913153003/


Inline methods of QuicBandwidth class.  No functional change; not
flag-protected.

Since "B" in "BBR" stands for bandwidth, we've been using
QuicBandwidth class much more actively on the hot paths.  The overhead
from calling QuicBandwidth methods started to show up on profiles, so
I've maked a CL to make them all inlined, as it was done with
QuicTime::Delta.

This removes the non-negativity check from the QuicBandwidth
constructor where it would previously result in a QUIC_BUG, since it's
now constexpr.

Merge internal change: 156806926
https://codereview.chromium.org/2921603002/


This QUIC change includes: 1) Change QuicStream's life
time. QuicStream is not deletable when it has unacked data (including
FIN). 2) Closed but not deletable QuicStream is moved to
zombie_streams in QuicSession. 3) Move ack listener to QuicStream. 4)
QuicHeaderStream keeps track of unacked headers which have not null
ack listener. 5) Both QuicStream and QuicSession implement
StreamNotifier which will be notified when stream frame is acked or
retransmitted.

Protected by FLAGS_quic_reloadable_flag_quic_use_stream_notifier.

Merge internal change: 156886444
https://codereview.chromium.org/2915873003/


Move tests from portable_quic to the new quic/quartc wrapper location.
n/a (test only, tests code that is only linked by Quartc)

Merge internal change: 156794055
https://codereview.chromium.org/2915993002/


Use BBR for Quartc congestion control.

We think BBR will do what we want in Quartc: generally avoid queuing
packets in the network and keep RTT low.  WebRTC does something
similar with its own bandwidth estimator.

We're starting work to optimize media flow, and we don't want to waste
effort optimizing on top of the wrong congestion control algorithm.
n/a (only linked by quartc)

Merge internal change: 156746324
https://codereview.chromium.org/2912393003/

BUG=
==========

to

==========
Landing Recent QUIC changes until 03:18 AM, May 28, UTC

Flags updated.
https://codereview.chromium.org/2920713002/

Default to BBR congestion control for QUIC. Protected by
FLAGS_quic_reloadable_flag_quic_default_to_bbr.

Merge internal change: 157287886
https://codereview.chromium.org/2917823004/


Remove is_deletable_ from QuicStream. Add QuicStream::IsWaitingForAcks which
returns true if stream is waiting for acks.

Merge internal change: 157256038
https://codereview.chromium.org/2916233002/


Remove QuicPacketNumberQueue::Complement() because it is no longer
used and will add work to the process of changing over to a deque from
an IntervalSet.

n/a (Test only)

Merge internal change: 157226948
https://codereview.chromium.org/2919733002/


Groundwork for cancelling quartc streams after a deadline is exceeded.

In the quic/quartc wrapper:
- Adds a method to QuartcSessionInterface to cancel a stream by number
- Fixes stream error code reporting
- Fixes spurious reset frames sent with QUIC_RST_STREAM_ACKNOWLEDGEMENT

This is done by number on QuartcSessionInterface instead of by a
method on a stream (or by passing the session a pointer to the stream)
because the quartc session owns quartc streams and may delete them
before the deadline.  Under the covers, the CancelStream method resets
a stream with error code 6 (QUIC_STREAM_CANCELLED).

QuartcStream currently only reports a non-zero error code if there's a
connection error.  This cl rectifies that by exposing both
stream_error() and connection_error() and letting callers examine
whichever one they want.

Since Quartc only sends on outgoing streams, it never sent a fin on
incoming streams.  This led to it not closing incoming streams
cleanly.  Whenever it closed an incoming stream, it sent a reset frame
with the error code QUIC_RST_STREAM_ACKNOWLEDGEMENT, in order to
communicate a final byte offset.  This isn't necessary, since we never
send anything (the final offset is always 0).  Instead, we now close
the reverse direction (sending on inbound streams, receiving on
outbound streams) immediately on stream creation, by simulating a fin.
This prevents spurious reset frames that look like errors.

In quartc:
- Adds CancelStream to the thread-safe wrapper
- Adds an optional parameter to SendOutgoingFrame to set a deadline
- Fixes incorrectly ordered boolean parameters in the
quartc_connection_test

SendOutgoingFrame will now schedule a task to cancel a stream if it is
given a non-infinite deadline.  The new deadline parameter defaults to
infinite to preserve current behavior.  We'll likely only use this for
video and audio streams, not for data and control streams.

n/a (only linked by quartc)
Merge internal change: 157132817


https://codereview.chromium.org/2913413002/
n/a (test-only change)

Merge internal change: 156881271
https://codereview.chromium.org/2913153003/


Inline methods of QuicBandwidth class.  No functional change; not
flag-protected.

Since "B" in "BBR" stands for bandwidth, we've been using
QuicBandwidth class much more actively on the hot paths.  The overhead
from calling QuicBandwidth methods started to show up on profiles, so
I've maked a CL to make them all inlined, as it was done with
QuicTime::Delta.

This removes the non-negativity check from the QuicBandwidth
constructor where it would previously result in a QUIC_BUG, since it's
now constexpr.

Merge internal change: 156806926
https://codereview.chromium.org/2921603002/


This QUIC change includes: 1) Change QuicStream's life
time. QuicStream is not deletable when it has unacked data (including
FIN). 2) Closed but not deletable QuicStream is moved to
zombie_streams in QuicSession. 3) Move ack listener to QuicStream. 4)
QuicHeaderStream keeps track of unacked headers which have not null
ack listener. 5) Both QuicStream and QuicSession implement
StreamNotifier which will be notified when stream frame is acked or
retransmitted.

Protected by FLAGS_quic_reloadable_flag_quic_use_stream_notifier.

Merge internal change: 156886444
https://codereview.chromium.org/2915873003/


Move tests from portable_quic to the new quic/quartc wrapper location.
n/a (test only, tests code that is only linked by Quartc)

Merge internal change: 156794055
https://codereview.chromium.org/2915993002/


Use BBR for Quartc congestion control.

We think BBR will do what we want in Quartc: generally avoid queuing
packets in the network and keep RTT low.  WebRTC does something
similar with its own bandwidth estimator.

We're starting work to optimize media flow, and we don't want to waste
effort optimizing on top of the wrong congestion control algorithm.
n/a (only linked by quartc)

Merge internal change: 156746324
https://codereview.chromium.org/2912393003/

BUG=

Review-Url: https://codereview.chromium.org/2916033003
Cr-Commit-Position: refs/heads/master@{#476570}
Committed:
https://chromium.googlesource.com/chromium/src/+/3c1d5ca822a369a0ef65d7044100...
==========

[commit-bot: I haz the power, 2017-06-02 04:52:36]

Committed patchset #5 (id:80001) as
https://chromium.googlesource.com/chromium/src/+/3c1d5ca822a369a0ef65d7044100...