Re: [virtio-comment] [PATCH v4 6/7] transport-fabrics: add device initialization

[Raphael Norwitz <raphael.norwitz@nutanix.com>]

> On Jun 26, 2023, at 3:25 AM, zhenwei pi <pizhenwei@bytedance.com> wrote:
> 
> Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
> ---
> transport-fabrics.tex | 33 +++++++++++++++++++++++++++++++++
> 1 file changed, 33 insertions(+)
> 
> diff --git a/transport-fabrics.tex b/transport-fabrics.tex
> index 75e4855..f7f29cf 100644
> --- a/transport-fabrics.tex
> +++ b/transport-fabrics.tex
> @@ -755,3 +755,36 @@ \subsubsection{RDMA}\label{sec:Virtio Transport Options / Virtio Over Fabrics /
> \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}
> +
> +
> +\subsection{Device Initialization}\label{sec:Virtio Transport Options / Virtio Over Fabrics / Device Initialization}
> +\begin{enumerate}
> +\item The Virtio-oF control queue must be established first by connecting
> +from the Virtio-oF initiator to the Virtio-oF target and issuing a
> +\nameref{sec:Virtio Transport Options / Virtio Over Fabrics / Commands Definition / Opcodes / Connect Command}
> +to create a Virtio-oF device instance.
> +\item Optionally, The Virtio-oF initiator issues a
> +\nameref{sec:Virtio Transport Options / Virtio Over Fabrics / Commands Definition / Opcodes / Get Feature Command}
> +to discover the features offered by the Virtio-oF device instance.
> +After feature negotiation, the Virtio-oF initiator also issues a
> +\nameref{sec:Virtio Transport Options / Virtio Over Fabrics / Commands Definition / Opcodes / Set Feature Command}
> +to finalize features.
> +\item The Virtio-oF initiator issues a
> +\nameref{sec:Virtio Transport Options / Virtio Over Fabrics / Commands Definition / Opcodes / Get Device ID Command}
> +and
> +\nameref{sec:Virtio Transport Options / Virtio Over Fabrics / Commands Definition / Opcodes / Get Vendor ID Command}
> +for virtio driver.
> +\item During virtio device initialization, the Virtio-oF initiator issues a
> +\nameref{sec:Virtio Transport Options / Virtio Over Fabrics / Commands Definition / Opcodes / Get Status Command}
> +and
> +\nameref{sec:Virtio Transport Options / Virtio Over Fabrics / Commands Definition / Opcodes / Set Status Command}.
> +\item Optionally, The Virtio-oF initiator issues a
> +\nameref{sec:Virtio Transport Options / Virtio Over Fabrics / Commands Definition / Opcodes / Get VQ Size Command}
> +to get the size of a Virtio-oF virtqueue.

This may be a good place to add a Get/Set request max scatter gather length?

> +\item The Virtio-oF initiator issues a
> +\nameref{sec:Virtio Transport Options / Virtio Over Fabrics / Commands Definition / Opcodes / Connect Command}
> +to establish a Virtio-oF virtqueue.
> +\item The Virtio-oF initiator creates Virtio-oF virtqueues one by one, then issues a
> +\nameref{sec:Virtio Transport Options / Virtio Over Fabrics / Commands Definition / Opcodes / VQ Command}
> +to supply virtqueue buffers to the Virtio-oF device instance on Virtio-oF virtqueues.
> +\end{enumerate}
> -- 
> 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/
> 
>