mirrors/arti.git/crates/tor-proto/src/channel/reactor.rs, branch arti-v1.3.0

Apply deferred rustfmt churn

2024-10-09T17:21:09Z

memquota: Use an mq_queue for channel->circuit RX queue

2024-10-09T17:19:41Z

Fixes #1682. (This involves some noise in the tests.)

memquota: Introduce type aliases for channel->circuit RX queue

2024-10-09T17:19:38Z

This is neater and will make changing the type (in a moment) less noisy.

tor-proto: Make circuit->channel queues participate in memquota

2024-10-03T14:10:47Z

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 site

2024-10-03T14:10:47Z

This gets it as far as the outbound circuit->channel mpsc queue creation. Also, we provide an accessor for it.

tor-proto: channel: Make construction fallible

2024-10-03T14:10:35Z

Making a channel is going to involve making a memquota Participant, which can fail.

extract tor_async_utils::oneshot into ::oneshot-fused-workaround

2024-08-28T14:27:46Z

Having this in the `tor-async-utils` crate prevents us from doing both of the following without introducing a circular dependency: * using it in `tor-rtmock` (which we currently do, particularly in tests). * using `tor-rtmock` to test things in `tor-async-utils`. We don't do this yet, but it is generally sensible to do so. In particular we want to move the `stream_peak` module there, which is currently tested with `tor-rtmock`. Moving this into its own crate avoids this circular dependency.

proto: Divide up some elements of ChannelDetails.

2024-05-16T16:24:12Z

Previously ChannelDetails had a double duty: It held elements shared among the clones of a Channel, and it also held elements shared between the Channel and the Reactor. But now that Channel doesn't have to implement Clone, we can more the non-Reactor elements into Channel itself. This change may improve cache locality a bit, and should make it a little easier to follow the channel code. I've also moved unique_id out of ChannelDetails into Channel _and_ Reactor: it is small, immutable, and used all the time in logging.

proto: Make Channel explicitly Arc<.>

2024-05-16T16:24:12Z

Previously, Channel was a type that you could Clone that implicitly its state. Now, Channel always appears as an Arc. This change has several benefits: * It makes the relationship between Channel struct and the underlying channel more clear. * It enables Channel to participate in the RPC system, where everything has to be an Arc<.> * It enables us to have a Weak, if we ever want to. * It will let us move various members out of ChannelDetails. We did this change a while ago with ClientCirc.

Downgrade some messages to trace

2023-11-29T18:51:30Z

These messages are very verbose and I doubt anyone will want them, usually, even when debugging.