summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2017-09-15 13:57:57 -0400
committerNick Mathewson <nickm@torproject.org>2017-09-15 13:57:57 -0400
commita1c495b4b97bd479d263960552fa103f1e09ffbe (patch)
treeb203c6db71be1c0dc5380c961b70e1957fdd1dbf
parent37302e64a4c53975bfb300bd46024d1eb503bd11 (diff)
downloadtor-a1c495b4b97bd479d263960552fa103f1e09ffbe.tar.gz
tor-a1c495b4b97bd479d263960552fa103f1e09ffbe.zip
Try to improve formatting on the Schedulers option
-rw-r--r--doc/tor.1.txt12
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/tor.1.txt b/doc/tor.1.txt
index c719bf51e2..4b33e1b477 100644
--- a/doc/tor.1.txt
+++ b/doc/tor.1.txt
@@ -790,16 +790,16 @@ GENERAL OPTIONS
(Default: KIST,KISTLite,Vanilla)
+
The possible scheduler types are:
-+
- KIST: Kernel Informed Socket Transport. Tor will use the kernel tcp
+ +
+ **KIST**: Kernel Informed Socket Transport. Tor will use the kernel tcp
information stack per-socket to make an informed decision on if it should
send or not the data. (Only available on Linux)
-+
- KISTLite: Same as KIST but without kernel support which means that tor
+ +
+ **KISTLite**: Same as KIST but without kernel support which means that tor
will use all the same mecanics as KIST but without the TCP information the
kernel can provide.
-+
- Vanilla: The scheduler that tor has always used that is do as much as
+ +
+ **Vanilla**: The scheduler that tor has always used that is do as much as
possible or AMAP.
[[KISTSchedRunInterval]] **KISTSchedRunInterval** __NUM__ **msec**::