diff options
| author | Stefano Brivio <sbrivio@redhat.com> | 2025-02-13 20:54:04 +0100 |
|---|---|---|
| committer | Stefano Brivio <sbrivio@redhat.com> | 2025-02-14 12:02:55 +0100 |
| commit | 71249ef3f9bcf1dbb2d6c13cdbc41ba88c794f06 (patch) | |
| tree | d243aa9356decc2f0e178ba51d26344a62d1eead /contrib | |
| parent | 30f1e082c3c0cee0a985b3c32e2b05280c596343 (diff) | |
| download | passt-71249ef3f9bcf1dbb2d6c13cdbc41ba88c794f06.tar passt-71249ef3f9bcf1dbb2d6c13cdbc41ba88c794f06.tar.gz passt-71249ef3f9bcf1dbb2d6c13cdbc41ba88c794f06.tar.bz2 passt-71249ef3f9bcf1dbb2d6c13cdbc41ba88c794f06.tar.lz passt-71249ef3f9bcf1dbb2d6c13cdbc41ba88c794f06.tar.xz passt-71249ef3f9bcf1dbb2d6c13cdbc41ba88c794f06.tar.zst passt-71249ef3f9bcf1dbb2d6c13cdbc41ba88c794f06.zip | |
tcp, tcp_splice: Don't set SO_SNDBUF and SO_RCVBUF to maximum values
I added this a long long time ago because it dramatically improved
throughput back then: with rmem_max and wmem_max >= 4 MiB, we would
force send and receive buffer sizes for TCP sockets to the maximum
allowed value.
This effectively disables TCP auto-tuning, which would otherwise allow
us to exceed those limits, as crazy as it might sound. But in any
case, it made sense.
Now that we have zero (internal) copies on every path, plus vhost-user
support, it turns out that these settings are entirely obsolete. I get
substantially the same throughput in every test we perform, even with
very short durations (one second).
The settings are not just useless: they actually cause us quite some
trouble on guest state migration, because they lead to huge queues
that need to be moved as well.
Drop those settings.
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'contrib')
0 files changed, 0 insertions, 0 deletions
