Commit ef4129e
faq: add GRO support info
At Netdev 0x19, there were some discussions about hardware GRO: Eric
reported that when comparing performances of TCP with MPTCP single-path,
a performance drop can be explained by hardware GRO not being used with
MPTCP.
Apparently, some NIC's skip hardware GRO in presence of "unknown" TCP
options: anything but TCP timestamps.
It then seems interesting to write this down in the FAQ to help people
understanding why hardware GRO might not be used with MPTCP. While at
it, explain that software GRO works when TSO was used on the sender
side.
Co-authored-by: Mat Martineau <[email protected]>
Signed-off-by: Matthieu Baerts (NGI0) <[email protected]>1 parent 9897b09 commit ef4129e
1 file changed
+22
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
210 | 210 | | |
211 | 211 | | |
212 | 212 | | |
| 213 | + | |
| 214 | + | |
| 215 | + | |
| 216 | + | |
| 217 | + | |
| 218 | + | |
| 219 | + | |
| 220 | + | |
| 221 | + | |
| 222 | + | |
| 223 | + | |
| 224 | + | |
| 225 | + | |
| 226 | + | |
| 227 | + | |
| 228 | + | |
| 229 | + | |
| 230 | + | |
| 231 | + | |
| 232 | + | |
| 233 | + | |
| 234 | + | |
213 | 235 | | |
214 | 236 | | |
215 | 237 | | |
| |||
0 commit comments