From: Stefan Hajnoczi <stefanha@redhat.com>
To: zhenwei pi <pizhenwei@bytedance.com>
Cc: parav@nvidia.com, mst@redhat.com, jasowang@redhat.com,
virtio-comment@lists.oasis-open.org, houp@yusur.tech,
helei.sig11@bytedance.com, zhouhuaping.san@bytedance.com,
xinhao.kong@duke.edu
Subject: [virtio-comment] Re: [PATCH v4 1/7] transport-fabrics: introduce Virtio Over Fabrics overview
Date: Wed, 15 Nov 2023 09:20:58 -0500 [thread overview]
Message-ID: <20231115142058.GA307546@fedora> (raw)
In-Reply-To: <20230626072551.1709389-2-pizhenwei@bytedance.com>
[-- Attachment #1: Type: text/plain, Size: 2656 bytes --]
On Mon, Jun 26, 2023 at 03:25:45PM +0800, zhenwei pi wrote:
> In the past years, virtio supports lots of device specifications by
> PCI/MMIO/CCW. These devices work fine in the virtualization environment.
>
> Introduce Virtio Over Fabrics transport to support "network attached
> peripheral devices". With this transport, Many Virtio based devices
> work over fabrics. Note that the balloon device may not make sense,
> shared memory regions won't work.
>
> Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
> ---
> content.tex | 1 +
> transport-fabrics.tex | 32 ++++++++++++++++++++++++++++++++
> 2 files changed, 33 insertions(+)
> create mode 100644 transport-fabrics.tex
>
> diff --git a/content.tex b/content.tex
> index d2ab9eb..bbbd79e 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -637,6 +637,7 @@ \chapter{Virtio Transport Options}\label{sec:Virtio Transport Options}
> \input{transport-pci.tex}
> \input{transport-mmio.tex}
> \input{transport-ccw.tex}
> +\input{transport-fabrics.tex}
>
> \chapter{Device Types}\label{sec:Device Types}
>
> diff --git a/transport-fabrics.tex b/transport-fabrics.tex
> new file mode 100644
> index 0000000..d10be2a
> --- /dev/null
> +++ b/transport-fabrics.tex
> @@ -0,0 +1,32 @@
> +\section{Virtio Over Fabrics}\label{sec:Virtio Transport Options / Virtio Over Fabrics}
> +
> +Virtio Over Fabrics (Virtio-oF) enables operations over fabrics that rely
> +primarily on message passing.
> +
> +Virtio-oF uses a reliable connection to transmit data. The reliable
> +connection facilitates communication between entities playing the following roles:
> +
> +\begin{itemize}
> +\item A Virtio-oF initiator functions as a Virtio-oF client.
> +The Virtio-oF initiator sends commands and associated data from the driver
> +to the Virtio-oF target.
> +\item A Virtio-oF target functions as a Virtio-oF server.
> +The Virtio-oF target forwards commands to the device and sends completions
> +and associated data back to the Virtio-oF initiator.
> +\end{itemize}
> +
> +Virtio-oF has the following features:
> +
> +\begin{itemize}
> +\item A Virtio-oF target is allowed to be connected by 0 or more Virtio-oF initiators.
> +\item A Virtio-oF initiator is allowed to connect to a single Virtio-oF target only.
> +A Virtio-oF device instance is a virtio device that the Virtio-oF initiator is
> +accessing through the Virtio-oF target.
Let's make sure the protocol is extensible so that multi-path or
persistent sessions (support for reconnect) are possible in the future.
They don't need to be there from the beginning.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-11-15 18:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 7:25 [virtio-comment] [PATCH v4 0/7] Introduce Virtio Over Fabrics zhenwei pi
2023-06-26 7:25 ` [virtio-comment] [PATCH v4 1/7] transport-fabrics: introduce Virtio Over Fabrics overview zhenwei pi
2023-07-29 23:23 ` Raphael Norwitz
2023-07-31 4:44 ` zhenwei pi
2023-08-01 0:20 ` Raphael Norwitz
2023-11-15 14:20 ` Stefan Hajnoczi [this message]
2023-06-26 7:25 ` [virtio-comment] [PATCH v4 2/7] transport-fabrics: introduce Virtio-oF Qualified Name zhenwei pi
2023-07-29 23:24 ` Raphael Norwitz
2023-06-26 7:25 ` [virtio-comment] [PATCH v4 3/7] transport-fabrics: introduce Virtio-oF Protocol Data Unit zhenwei pi
2023-07-29 23:25 ` Raphael Norwitz
2023-07-31 2:28 ` zhenwei pi
2023-06-26 7:25 ` [virtio-comment] [PATCH v4 4/7] transport-fabrics: introduce command set zhenwei pi
2023-06-27 9:04 ` [virtio-comment] " Jason Wang
2023-06-28 1:34 ` [virtio-comment] " zhenwei pi
2023-06-28 2:56 ` Jason Wang
2023-06-28 6:53 ` [virtio-comment] " zhenwei pi
2023-07-29 23:28 ` [virtio-comment] " Raphael Norwitz
2023-07-31 2:34 ` zhenwei pi
2023-08-01 0:25 ` Raphael Norwitz
2023-08-01 2:00 ` zhenwei pi
2023-06-26 7:25 ` [virtio-comment] [PATCH v4 5/7] transport-fabrics: introduce transport binding zhenwei pi
2023-07-29 23:28 ` Raphael Norwitz
2023-07-31 2:36 ` zhenwei pi
2023-06-26 7:25 ` [virtio-comment] [PATCH v4 6/7] transport-fabrics: add device initialization zhenwei pi
2023-07-29 23:29 ` Raphael Norwitz
2023-06-26 7:25 ` [virtio-comment] [PATCH v4 7/7] transport-fabrics: introduce keyed eager buffers zhenwei pi
2023-07-29 23:30 ` Raphael Norwitz
2023-07-31 3:21 ` zhenwei pi
2023-07-19 7:07 ` [virtio-comment] PING: [PATCH v4 0/7] Introduce Virtio Over Fabrics zhenwei pi
2023-07-19 12:44 ` [virtio-comment] " Parav Pandit
2023-07-19 12:48 ` [virtio-comment] " Michael S. Tsirkin
2023-07-20 2:32 ` [virtio-comment] " zhenwei pi
2023-07-20 2:34 ` [virtio-comment] " Parav Pandit
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=20231115142058.GA307546@fedora \
--to=stefanha@redhat.com \
--cc=helei.sig11@bytedance.com \
--cc=houp@yusur.tech \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=pizhenwei@bytedance.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=xinhao.kong@duke.edu \
--cc=zhouhuaping.san@bytedance.com \
/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).