diff options
| author | David Gibson <david@gibson.dropbear.id.au> | 2025-03-26 14:44:06 +1100 |
|---|---|---|
| committer | Stefano Brivio <sbrivio@redhat.com> | 2025-03-26 21:34:32 +0100 |
| commit | 37d78c9ef3944c1b060e3e8259b82fea3f8ec6bf (patch) | |
| tree | 54cbf8593895ab63bdb72b3304dccbb2f4af220d /contrib/qemu | |
| parent | f67c488b81ca2a4d9f819b625fceab10b71fc3a5 (diff) | |
| download | passt-37d78c9ef3944c1b060e3e8259b82fea3f8ec6bf.tar passt-37d78c9ef3944c1b060e3e8259b82fea3f8ec6bf.tar.gz passt-37d78c9ef3944c1b060e3e8259b82fea3f8ec6bf.tar.bz2 passt-37d78c9ef3944c1b060e3e8259b82fea3f8ec6bf.tar.lz passt-37d78c9ef3944c1b060e3e8259b82fea3f8ec6bf.tar.xz passt-37d78c9ef3944c1b060e3e8259b82fea3f8ec6bf.tar.zst passt-37d78c9ef3944c1b060e3e8259b82fea3f8ec6bf.zip | |
udp: Always hash socket facing flowsides
For UDP packets from the tap interface (like TCP) we use a hash table to
look up which flow they belong to. Unlike TCP, we sometimes also create a
hash table entry for the socket side of UDP flows. We need that when we
receive a UDP packet from a "listening" socket which isn't specific to a
single flow.
At present we only do this for the initiating side of flows, which re-use
the listening socket. For the target side we use a connected "reply"
socket specific to the single flow.
We have in mind changes that maye introduce some edge cases were we could
receive UDP packets on a non flow specific socket more often. To allow for
those changes - and slightly simplifying things in the meantime - always
put both sides of a UDP flow - tap or socket - in the hash table. It's
not that costly, and means we always have the option of falling back to a
hash lookup.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'contrib/qemu')
0 files changed, 0 insertions, 0 deletions
