chore: remove WindowUpdateMode::OnReceive
#179
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
thomaseizinger
approved these changes
Nov 23, 2023
yamux/src/connection.rs
Outdated
| } | ||
| // The remote has either still credit or will be given more | ||
| // (due to an enqueued window update or because the update | ||
| // mode is `OnReceive`) or we already have inbound frames in |
|
Moving forward here. In case we want to cut a patch release of the |
Comment on lines
+505
to
+511
| // The remote has either still credit or will be given more | ||
| // due to an enqueued window update or we already have | ||
| // inbound frames in the socket buffer which will be | ||
| // processed later. In any case we will reply with an RST in | ||
| // `Connection::on_data` because the stream will no longer | ||
| // be known. | ||
| None |
lexnv
added a commit
to paritytech/litep2p
that referenced
this pull request
Jan 29, 2025
… API (#320) This PR relies on the libp2p-yamux crate for the core functionality of our multiplexer. The main goal is to bring complete compatibility between libp2p and litep2p on the yamux layer, and remove 90% of the yamux code in favor of the upstream implementation while keeping the controller API in place. The upstream crate brings in multiple fixes for substreams while minimally impacting our dependency tree. The downside of the upstream implementation is that the controller API has been removed. Adjusting to the new API would be a massive breaking change for all transport layers. Therefore, we keep the controller API which integrates seamlessly with the upstream yamux. No other changes were present to the controller API in the upstream implementation. ### Yamux changelog The changelog includes the fixes from the upstream since the moment we have inlined the crate in litep2p: ``` # 0.13.4 - Fix sending pending frames after closing. See [PR 194](libp2p/rust-yamux#194). # 0.13.3 - Wake up readers after setting the state to RecvClosed to not miss EOF. See [PR 190](libp2p/rust-yamux#190). - Use `web-time` instead of `instant`. See [PR 191](libp2p/rust-yamux#191). # 0.13.2 - Bound `Active`'s `pending_frames` to enforce backpressure. See [460baf2](libp2p/rust-yamux@460baf2) # 0.13.1 - Fix WASM support using `instant::{Duration, Instant}` instead of `std::time::{Duration, Instant}`. See [PR 179](libp2p/rust-yamux#179). # 0.13.0 - Introduce dynamic stream receive window auto-tuning. While low-resourced deployments maintain the benefit of small buffers, high resource deployments eventually end-up with a window of roughly the bandwidth-delay-product (ideal) and are thus able to use the entire available bandwidth. See [PR 176](libp2p/rust-yamux#176) for performance results and details on the implementation. - Remove `WindowUpdateMode`. Behavior will always be `WindowUpdateMode::OnRead`, thus enabling flow-control and enforcing backpressure. See [PR 178](libp2p/rust-yamux#178). # 0.12.1 - Deprecate `WindowUpdateMode::OnReceive`. It does not enforce flow-control, i.e. breaks backpressure. Use `WindowUpdateMode::OnRead` instead. See [PR #177](libp2p/rust-yamux#177). # 0.12.0 - Remove `Control` and `ControlledConnection`. Users have to move to the `poll_` functions of `Connection`. See [PR #164](libp2p/rust-yamux#164). - Fix a bug where `Stream`s would not be dropped until their corresponding `Connection` was dropped. See [PR #167](libp2p/rust-yamux#167). ``` ### Next Steps - [x] deployment in versi-net and monitor metrics / CPU impact (extensively test this) cc @paritytech/networking --------- Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow up to previous deprecation #177.
Fixes #175.