@@ -77,13 +77,13 @@ if necessary.
77
77
values that we've tuned up. In this way, we can let the system
78
78
find a balance between providing resources and exhausting them.
79
79
In some cases, we won't need to tune up values; they may be fine
80
- as they are. But in other cases limits block optimal performance,
80
+ as they are. But in other cases these limits block optimal performance,
81
81
and if they are raised safely - with awareness of global memory
82
82
limits - we can get out the way of improved performance. Another
83
83
concern is that increasing buffer size leads to latency - to
84
84
handle that, we correlate buffer size changes and TCP smoothed
85
85
round-trip time; if the correlation between these exceeds a
86
- threshould (0.7) we stop increasing buffer size.
86
+ threshold (0.7) we stop increasing buffer size.
87
87
88
88
## Concepts
89
89
@@ -192,7 +192,7 @@ $ sudo service bpftune start
192
192
$ sudo systemctl enable bpftune
193
193
```
194
194
195
- bpftune logs to syslog so /var/log/messags will contain details
195
+ bpftune logs to syslog so /var/log/messages will contain details
196
196
of any tuning carried out.
197
197
198
198
bpftune can also be run in the foreground as a program; to redirect
@@ -317,4 +317,4 @@ bpftune: sysctl 'net.ipv4.tcp_rmem' changed from (4096 131072 1310720 ) -> (4096
317
317
## For more info
318
318
319
319
See the docs/ subdirectory for manual pages covering bpftune
320
- and assoiated tuners.
320
+ and associated tuners.
0 commit comments