diff options
| author | Andrea Shepard <andrea@torproject.org> | 2013-11-05 00:30:02 -0800 |
|---|---|---|
| committer | Andrea Shepard <andrea@torproject.org> | 2014-09-30 22:49:03 -0700 |
| commit | 8852a1794cfa9eb5dae494f5d85242d8fd6955fc (patch) | |
| tree | 266daad8c0e03603a5e8e473cafaa8c2166d7832 /src/or/connection.c | |
| parent | 7674308f622904bc5a4cff5e7cb4d0f22fbf84d7 (diff) | |
| download | tor-8852a1794cfa9eb5dae494f5d85242d8fd6955fc.tar.gz tor-8852a1794cfa9eb5dae494f5d85242d8fd6955fc.zip | |
Track total queue size per channel, with overhead estimates, and global queue total
Diffstat (limited to 'src/or/connection.c')
| -rw-r--r-- | src/or/connection.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/src/or/connection.c b/src/or/connection.c index 4a3bd2cf03..525f4b5e85 100644 --- a/src/or/connection.c +++ b/src/or/connection.c @@ -3839,6 +3839,8 @@ connection_handle_write_impl(connection_t *conn, int force) tor_tls_get_n_raw_bytes(or_conn->tls, &n_read, &n_written); log_debug(LD_GENERAL, "After TLS write of %d: %ld read, %ld written", result, (long)n_read, (long)n_written); + or_conn->bytes_xmitted += result; + or_conn->bytes_xmitted_by_tls += n_written; /* So we notice bytes were written even on error */ /* XXXX024 This cast is safe since we can never write INT_MAX bytes in a * single set of TLS operations. But it looks kinda ugly. If we refactor |