Re: Re: [virtio-comment] [PATCH v4 5/7] transport-fabrics: introduce transport binding

[zhenwei pi <pizhenwei@bytedance.com>]

On 7/30/23 07:28, Raphael Norwitz wrote:
> > On Jun 26, 2023, at 3:25 AM, zhenwei pi <pizhenwei@bytedance.com> wrote:
> >
> > Add TCP/IP, TLS TCP/IP, RDMA transports.
> >
> > Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
> > ---
> > transport-fabrics.tex | 26 ++++++++++++++++++++++++++
> > 1 file changed, 26 insertions(+)
> >
> > diff --git a/transport-fabrics.tex b/transport-fabrics.tex
> > index 3fd9e8e..75e4855 100644
> > --- a/transport-fabrics.tex
> > +++ b/transport-fabrics.tex
> > @@ -729,3 +729,29 @@ \subsubsection{Opcodes}\label{sec:Virtio Transport Options / Virtio Over Fabrics
> > \paragraph{Keepalive Completion}\label{sec:Virtio Transport Options / Virtio Over Fabrics / Commands Definition / Opcodes / Keepalive Completion}
> > A Keepalive Completion is used as a health check mechanism to detect when a Virtio-oF initiator becomes unavailable, it is used by a Virtio-oF device instance for the Virtio-oF control queue only.
> > Once the Virtio-oF initiator becomes unavailable, the Virtio-oF target should destroy the Virtio-oF device instance and associated resources.
> > +
> > +
> > +\subsection{Transport Binding}\label{sec:Virtio Transport Options / Virtio Over Fabrics / Transport Binding}
> > +
> > +\subsubsection{TCP/IP}\label{sec:Virtio Transport Options / Virtio Over Fabrics / Transport Binding / TCP IP}
> > +Virtio-oF supports both TCP/IPv4 and TCP/IPv6, it uses
> > +\nameref{sec:Virtio Transport Options / Virtio Over Fabrics / Protocol Data Unit/ Stream Data Transfers}.
> > +A TCP/IP based Virtio-oF target uses port 8549 (CRC-16/ARC of "Virtio") by default.
> > +
> > +\subsubsection{TLS TCP/IP}\label{sec:Virtio Transport Options / Virtio Over Fabrics / Transport Binding / TLS TCP IP}
> > +Virtio-oF supports both TLS v1.2 and TLS v1.3 over the underlying TCP/IPv4 and TCP/IPv6, it uses
> > +\nameref{sec:Virtio Transport Options / Virtio Over Fabrics / Protocol Data Unit/ Stream Data Transfers}.
> > +A TLS TCP/IP based Virtio-oF target uses port 8549 (CRC-16/ARC of "Virtio") by default.
> > +
> > +\subsubsection{RDMA}\label{sec:Virtio Transport Options / Virtio Over Fabrics / Transport Binding / RDMA}
> > +Virtio-oF supports RDMA, it uses
> > +\nameref{sec:Virtio Transport Options / Virtio Over Fabrics / Protocol Data Unit/ Keyed Data Transfers}.
> > +A RoCEv2 based Virtio-oF target uses UDP port 8549 (CRC-16/ARC of "Virtio") by default, and a iWARP based Virtio-oF target uses TCP port 8549 by default.
> > +
> > +RDMA uses the following operations:
> > +\begin{itemize}
> > +\item The Virtio-oF initiator sends a PDU by RDMA SEND.
>
> What about with âeager buffersâ? It probably uses RDMA write for those?

Yes, the target side exposes a MR, the initiator side use RDMA WRITE to 
access it.

> > +\item The Virtio-oF target reads the remote data by RDMA SEND.
>
> I assume you meant the target reads with RDMA read?

Thanks, I'll fix this.

> > +\item The Virtio-oF target writes the remote data by RDMA WRITE.
> > +\item The Virtio-oF target sends a PDU by RDMA SEND.
> > +\end{itemize}
> > --
> > 2.25.1
> >
> >
> > This publicly archived list offers a means to provide input to the
> > OASIS Virtual I/O Device (VIRTIO) TC.
> >
> > In order to verify user consent to the Feedback License terms and
> > to minimize spam in the list archive, subscription is required
> > before posting.
> >
> > Subscribe: virtio-comment-subscribe@lists.oasis-open.org
> > Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
> > List help: virtio-comment-help@lists.oasis-open.org
> > List archive: https://lists.oasis-open.org/archives/virtio-comment/
> > Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
> > List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
> > Committee: https://www.oasis-open.org/committees/virtio/
> > Join OASIS: https://www.oasis-open.org/join/

--
zhenwei pi