0f938c3b9a
Our allocation scheme for flow entries means there are some non-obvious constraints on when what things can be done with an entry. Add a big doc comment explaining the life cycle. In addition, make a FLOW_START() macro to mark one of the important transitions. This encourages correct usage, by making it natural to only access the flow type specific structure after calling it. It also logs that a new flow has been created, which is useful for debugging. We also add logging when a flow's lifecycle ends. This doesn't need a new helper, because it can only happen either from flow_alloc_cancel() or from the flow deferred handler. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
19 lines
539 B
C
19 lines
539 B
C
/* SPDX-License-Identifier: GPL-2.0-or-later
|
|
* Copyright (c) 2022 Red Hat GmbH
|
|
* Author: Stefano Brivio <sbrivio@redhat.com>
|
|
*/
|
|
|
|
#ifndef TCP_SPLICE_H
|
|
#define TCP_SPLICE_H
|
|
|
|
struct tcp_splice_conn;
|
|
union sockaddr_inany;
|
|
|
|
void tcp_splice_sock_handler(struct ctx *c, union epoll_ref ref,
|
|
uint32_t events);
|
|
bool tcp_splice_conn_from_sock(const struct ctx *c,
|
|
union tcp_listen_epoll_ref ref, union flow *flow,
|
|
int s, const union sockaddr_inany *sa);
|
|
void tcp_splice_init(struct ctx *c);
|
|
|
|
#endif /* TCP_SPLICE_H */
|