mirrors/arti.git/crates/tor-proto/src/channel, branch arti-v1.3.2mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.22024-12-10T19:15:16Ztor-proto: replace `Channel`s "closed" state handling2024-12-10T19:15:16ZSteven Engleropara@torproject.org2024-11-26T02:54:44Zurn:sha1:09d7bce115179c3b7c4cb55cd1e0127fbe9e9929
Previously `Channel` had two concepts of "closed". There was an atomic
flag that was set to `true` at the end `Reactor::run`, and an
experimental oneshot channel where the sender was dropped when the
reactor was dropped.
This commit consolidates these two using the `oneshot_broadcast` module.
This means that the behaviour is consistent between both "closed"
statuses (`is_closing()` and `wait_for_close()`). A channel is
considered closed when its reactor is dropped.
This also helps progress towards making the channel reactor cancellation
safe (see arti#1756).
tor-proto: Specify which of the 2 senders is used for sending cells.2024-11-20T10:53:24ZGabriela Moldovangabi@torproject.org2024-11-19T10:52:52Zurn:sha1:0839b034d3fa28f7184dd7fae8ef866220cb7ecdApply deferred rustfmt churn2024-10-09T17:21:09ZIan Jacksonijackson@chiark.greenend.org.uk2024-10-09T17:21:09Zurn:sha1:fafe03628c3a6f670b052cfa8ac782843d72ea1amemquota: Use an mq_queue for channel->circuit RX queue2024-10-09T17:19:41ZIan Jacksonijackson@chiark.greenend.org.uk2024-10-09T16:45:07Zurn:sha1:bfa67c34da9357e412758507c312c6b92c2f3133
Fixes #1682.
(This involves some noise in the tests.)
memquota: Introduce type aliases for channel->circuit RX queue2024-10-09T17:19:38ZIan Jacksonijackson@chiark.greenend.org.uk2024-10-09T16:43:33Zurn:sha1:6fd94b3d2547d54aa4e9bf5282f72064c6a6ef3f
This is neater and will make changing the type (in a moment) less
noisy.
tor-proto: Make circuit->channel queues participate in memquota2024-10-03T14:10:47ZIan Jacksonijackson@chiark.greenend.org.uk2024-09-24T11:12:25Zurn:sha1:39935609efa1feb7512af8cf401865b90ffed786
We use the *channel*'s memquota account. This is arguably wrong, but
it's hard to get right now. See #1652.
Change the type of the queue, and the places it's constructed.
The use sites can all stay the same.
tor-proto: Plumb the ChannelAccount through to queue creation site2024-10-03T14:10:47ZIan Jacksonijackson@chiark.greenend.org.uk2024-10-02T16:24:59Zurn:sha1:939d291ed3792a5fd1392f4e2816de254ac1bc12
This gets it as far as the outbound circuit->channel mpsc queue creation.
Also, we provide an accessor for it.
tor-proto: Plumb the ChannelAccount through to queue creation site (pre-fmt)2024-10-03T14:10:35ZIan Jacksonijackson@chiark.greenend.org.uk2024-10-02T15:32:47Zurn:sha1:17f55b3302cb254506f0ce2a3421211b55eb5bc4tor-proto: channel: Make construction fallible2024-10-03T14:10:35ZIan Jacksonijackson@chiark.greenend.org.uk2024-09-23T10:19:32Zurn:sha1:1861de6a00edd99c4354fc3b2eaaf88fec2d4fe6
Making a channel is going to involve making a memquota Participant,
which can fail.
tor-proto: Add a CoarseTimeProvider bound to all the SleepProviders (fmt)2024-10-01T18:05:25ZIan Jacksonijackson@chiark.greenend.org.uk2024-10-01T17:43:59Zurn:sha1:88d6f90b13fd8d0ddb538f833ff9531f8d308047