On Tue Jun 9, 2026 at 2:32 PM CEST, Aaron Conole wrote: > "Gaetan Rivet" <[email protected]> writes: [...] > >> -struct conn_tcp { > >> - struct conn up; > >> - struct tcp_peer peer[2]; /* 'conn' lock protected. */ > >> -}; > >> +ct_private_id_t conntrack_tcp_private_id = CT_PRIVATE_ID_INVALID; > > > > Hi, > > > > Should each L4 proto register their own private ID, or could it be > > shared? I.e. have a single `conntrack_l4_private_id`, that would be used > > by all l4protos (and other modules) to access L4 private data? > > I'm not sure - different L4 protocols would have different state > objects. Ex, SCTP would track much more than this, and UDP doesn't > track near this much. Or I guess you mean that we just reuse the ID, > because the protocol reader would determine how the block gets > interpreted. I think that makes sense, and I can look into it.
Exactly yes. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
