-
Notifications
You must be signed in to change notification settings - Fork 1
/
report-automtud.xml
48 lines (40 loc) · 1.64 KB
/
report-automtud.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
<!-- Please send your reports to: [email protected] -->
<project cat='proj'>
<title>automtud: Better Jumbo Frame Support</title>
<!-- Required section -->
<contact>
<person>
<name>
<given>John-Mark</given>
<common>Gurney</common>
</name>
<email>[email protected]</email>
</person>
</contact>
<links>
<url href="https://github.com/jmgurney/automtud">jmgurney/automtud on github</url>
</links>
<body>
<p>The automtud script will allow a FreeBSD machine to send
jumbo frames to machines that support them, while using normal
sized frames for other machines.</p>
<p>There are various advantages to using jumbo frames, such as
reduced protocol overhead. It also means that TCP streams will
not be segmented as much (though TSO helps) and in cases where
LRO doesn't work well, less packets will be received.</p>
<p>The script does not currently restore the state of the system
it was in before starting. This means that you'll have to manually
change the interface MTU, and manually delete host routes.</p>
</body>
<help>
<task>Fix up various ethernet drivers to better support jumbo frames.
Most ethernet drivers, though supporting scatter/gather, use a
physically contiguous zone which can cause resource shortages.</task>
<task>More testing is needed to ensure that things behave as
expected. This means that when running the script, all machines
work as expected w/o slow down or connectivity issues. Check
`vmstat -z | grep mbuf' to ensure this isn't a problem with running
out of jumbo_9k or jumbo_16k buffers do to ethernet driver
issue.</task>
</help>
</project>