diff options
| author | David Gibson <david@gibson.dropbear.id.au> | 2023-08-22 15:29:58 +1000 |
|---|---|---|
| committer | Stefano Brivio <sbrivio@redhat.com> | 2023-08-22 12:15:36 +0200 |
| commit | b60fa33eeafbe2d73d3a4cb6586dd4d637751fa7 (patch) | |
| tree | 8be1d614dad751b9bb746944eee48ec9e5c3d8b6 /test/run | |
| parent | 955dd3251c9e9b0a1469015748e4600f68e8de0a (diff) | |
| download | passt-b60fa33eeafbe2d73d3a4cb6586dd4d637751fa7.tar passt-b60fa33eeafbe2d73d3a4cb6586dd4d637751fa7.tar.gz passt-b60fa33eeafbe2d73d3a4cb6586dd4d637751fa7.tar.bz2 passt-b60fa33eeafbe2d73d3a4cb6586dd4d637751fa7.tar.lz passt-b60fa33eeafbe2d73d3a4cb6586dd4d637751fa7.tar.xz passt-b60fa33eeafbe2d73d3a4cb6586dd4d637751fa7.tar.zst passt-b60fa33eeafbe2d73d3a4cb6586dd4d637751fa7.zip | |
tcp: Move in_epoll flag out of common connection structure
The in_epoll boolean is one of only two fields (currently) in the common
structure shared between tap and spliced connections. It seems like it
belongs there, because both tap and spliced connections use it, and it has
roughly the same meaning.
Roughly, however, isn't exactly: which fds this flag says are in the epoll
varies between the two connection types, and are in type specific fields.
So, it's only possible to meaningfully use this value locally in type
specific code anyway.
This common field is going to get in the way of more widespread
generalisation of connection / flow tracking, so move it to separate fields
in the tap and splice specific structures.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'test/run')
0 files changed, 0 insertions, 0 deletions