Hi Ryan, A concrete driver for AF_VSOCK is the microVM / confidential-computing space (e.g., Nitro Enclaves) where vsock is the standard host↔guest channel, and also Kata Containers where vsock is used for host/agent comms.
Thanks, Arturo On Sat, Feb 14, 2026 at 12:48 PM Michael Osipov <[email protected]> wrote: > Guys, not forget AF_HYPERV :-D > > Sample impl from Microsoft: > https://github.com/freebsd/freebsd-src/blob/625dc44832cd760be3d7242d8e21a530c7e32bfc/sys/dev/hyperv/hvsock/hv_sock.c#L110 > > On 2026/02/13 16:36:42 Ryan Schmitt wrote: > > There are lots of exotic socket types, including various non-portable > > subtypes of Unix domain sockets. What are people actually asking for? In > > the docker-java client for example, we found... aftermarket support for > > both Unix domain sockets and named pipes (as a kind of ersatz UDS for > older > > versions of Windows), but no AF_VSOCK. > > > > On Thu, Feb 12, 2026 at 10:38 AM Arturo Bernal <[email protected]> > wrote: > > > > > Hi Ryan, > > > > > > Now that UDS support is in, do you think it makes sense to also > upstream > > > AF_VSOCK as an optional follow-up? > > > > > > I’m thinking: same route/pool-key + custom connection-operator > pattern, but > > > gated behind a builder flag and backed by JUnixSocket’s vsock module > (so > > > “JUnixSocket-only”, Linux/VM focused). > > > > > > Thanks, > > > > > > > > > On Fri, May 30, 2025 at 9:33 PM Ryan Schmitt <[email protected]> > wrote: > > > > > > > OK, I'll do it. > > > > > > > > On Fri, May 30, 2025 at 2:27 AM Oleg Kalnichevski <[email protected]> > > > > wrote: > > > > > > > > > > On Thu, 2025-05-29 at 15:44 -0700, Ryan Schmitt wrote: > > > > > > Do we have any existing integration test coverage for socket and > > > > > > connection timeouts? I only see mock-based unit tests. > > > > > > > > > > > > > > > > We do not. Timeouts are quite difficult to test reliably and up to > now > > > > > no one stepped forth to put efforts into building them. > > > > > > > > > > Oleg > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [email protected] > > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [email protected] > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
