aboutgitcodebugslistschat
path: root/test
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2023-11-30 13:02:18 +1100
committerStefano Brivio <sbrivio@redhat.com>2023-12-04 09:51:24 +0100
commit705549f83494ebd23987e87de38045d8200b4efd (patch)
treed7dc4ca2516549e3c2f1e2b2252ffedd176d243e /test
parent788d2fe3ce7231b520b139712d721e9d481b49ea (diff)
downloadpasst-705549f83494ebd23987e87de38045d8200b4efd.tar
passt-705549f83494ebd23987e87de38045d8200b4efd.tar.gz
passt-705549f83494ebd23987e87de38045d8200b4efd.tar.bz2
passt-705549f83494ebd23987e87de38045d8200b4efd.tar.lz
passt-705549f83494ebd23987e87de38045d8200b4efd.tar.xz
passt-705549f83494ebd23987e87de38045d8200b4efd.tar.zst
passt-705549f83494ebd23987e87de38045d8200b4efd.zip
flow,tcp: Use epoll_ref type including flow and side
Currently TCP uses the 'flow' epoll_ref field for both connected sockets and timers, which consists of just the index of the relevant flow (connection). This is just fine for timers, for while it obviously works, it's subtly incomplete for sockets on spliced connections. In that case we want to know which side of the connection the event is occurring on as well as which connection. At present, we deduce that information by looking at the actual fd, and comparing it to the fds of the sockets on each side. When we use the flow table for more things, we expect more cases where something will need to know a specific side of a specific flow for an event, but nothing more. Therefore add a new 'flowside' epoll_ref field, with exactly that information. We use it for TCP connected sockets. This allows us to directly know the side for spliced connections. For "tap" connections, it's pretty meaningless, since the side is always the socket side. It still makes logical sense though, and it may become important for future flow table work. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions