From: Bobby Eshleman <bobbyeshleman@gmail.com>
To: ksummit@lists.linux.dev
Cc: bobby.eshleman@bytedance.com, amery.hung@bytedance.com,
cong.wang@bytedance.com
Subject: [TECH TOPIC] VSOCK: From Convenience to Performant VirtIO Communication
Date: Tue, 1 Aug 2023 07:06:28 +0000 [thread overview]
Message-ID: <ZMiu9Mkdg4wHtCs7@bullseye> (raw)
Below is the abstract for talk we are proposing for LPC2023 about recent
work and advancements in the VSOCK socket family.
Thanks in advance!
Bobby Eshleman
Abstract
The VSOCK family of sockets has traditionally been embraced for its
convenience in enabling communication between virtual machines and the
host in virtualized environments. However, recent practical advancements
have developed VSOCK into more than just a convenience; it has become a
viable networking protocol even for some extremely demanding networking
workloads across the host/VM boundary. This talk will delve into
virtio/vsock and its new support for datagrams, unlocking new potential
for efficient packet exchange between VMs and the host. By comparing
VSOCK datagrams with UDP over virtio, we showcase its practical
performance advantages, making it a compelling choice for
high-throughput point-to-point socket-based communication scenarios.
Additionally, we'll explore the integration of sockmap for VSOCK,
empowering eBPF programs to interact with VSOCK sockets within the
kernel. This capability allows for dynamic socket management, providing
the ability to leverage the performance advantages of both sockmap and
VSOCK in the same practical applications.
reply other threads:[~2023-08-01 18:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZMiu9Mkdg4wHtCs7@bullseye \
--to=bobbyeshleman@gmail.com \
--cc=amery.hung@bytedance.com \
--cc=bobby.eshleman@bytedance.com \
--cc=cong.wang@bytedance.com \
--cc=ksummit@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).