diff options
author | David Gibson <david@gibson.dropbear.id.au> | 2024-11-27 14:54:07 +1100 |
---|---|---|
committer | Stefano Brivio <sbrivio@redhat.com> | 2024-11-28 14:03:16 +0100 |
commit | 08ea3cc581beed16afff3fa934f31cbdb82cbb95 (patch) | |
tree | 653247ea43465b8b8f542f1b1fb8b633a28783b0 /pasta.c | |
parent | 2ee07697c4ab4f4efff6431aaa787f21bcc6f1d1 (diff) | |
download | passt-08ea3cc581beed16afff3fa934f31cbdb82cbb95.tar passt-08ea3cc581beed16afff3fa934f31cbdb82cbb95.tar.gz passt-08ea3cc581beed16afff3fa934f31cbdb82cbb95.tar.bz2 passt-08ea3cc581beed16afff3fa934f31cbdb82cbb95.tar.lz passt-08ea3cc581beed16afff3fa934f31cbdb82cbb95.tar.xz passt-08ea3cc581beed16afff3fa934f31cbdb82cbb95.tar.zst passt-08ea3cc581beed16afff3fa934f31cbdb82cbb95.zip |
tcp: Pass TCP header and payload separately to tcp_fill_headers[46]()
At the moment these take separate pointers to the tap specific and IP
headers, but expect the TCP header and payload as a single tcp_payload_t.
As well as being slightly inconsistent, this involves some slightly iffy
pointer shenanigans when called on the flags path with a tcp_flags_t
instead of a tcp_payload_t.
More importantly, it's inconvenient for the upcoming vhost-user case, where
the TCP header and payload might not be contiguous. Furthermore, the
payload itself might not be contiguous.
So, pass the TCP header as its own pointer, and the TCP payload as an IO
vector.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'pasta.c')
0 files changed, 0 insertions, 0 deletions