Re: [PATCH net-next v4 08/15] quic: add path management
Xin Long <[email protected]> Wed, 5 Nov 2025 20:28:08 -0500
| Newsgroups | dev.linux.lists.quic,dev.linux.lists.kernel-tls-handshake,org.kernel.vger.linux-cifs,org.kernel.vger.netdev |
|---|---|
| Message-ID | <CADvbK_dDMA5UkS8LDqSkFwg-H2p1DNqqP_4Tv7ie1hqNp-Yrrg@mail.gmail.com> |
On Tue, Nov 4, 2025 at 6:50 AM Paolo Abeni <[email protected]> wrote: > > On 10/29/25 3:35 PM, Xin Long wrote: > > This patch introduces 'quic_path_group' for managing paths, represented > > by 'struct quic_path'. A connection may use two paths simultaneously > > for connection migration. > > > > Each path is associated with a UDP tunnel socket (sk), and a single > > UDP tunnel socket can be related to multiple paths from different sockets. > > These UDP tunnel sockets are wrapped in 'quic_udp_sock' structures and > > stored in a hash table. > > > > It includes mechanisms to bind and unbind paths, detect alternative paths > > for migration, and swap paths to support seamless transition between > > networks. > > > > - quic_path_bind(): Bind a path to a port and associate it with a UDP sk. > > > > - quic_path_free(): Unbind a path from a port and disassociate it from a > > UDP sk. > > I find the above name slightly misleading, as I expect such function to > free the path argument. Possibly quic_path_unbind? > Makes sense. Thanks.