From: zhenwei pi <pizhenwei@bytedance.com>
To: stefanha@redhat.com, mst@redhat.com, parav@nvidia.com,
jasowang@redhat.com
Cc: virtio-comment@lists.oasis-open.org, houp@yusur.tech,
xinhao.kong@duke.edu, helei.sig11@bytedance.com,
zhouhuaping.san@bytedance.com,
zhenwei pi <pizhenwei@bytedance.com>
Subject: [virtio-comment] [PATCH v3 0/7] Introduce Virtio Over Fabrics
Date: Mon, 19 Jun 2023 16:31:24 +0800 [thread overview]
Message-ID: <20230619083131.1544999-1-pizhenwei@bytedance.com> (raw)
v2 -> v3:
[PATCH v2 01/11] transport-fabrics: introduce Virtio Over Fabrics
- Drop referring to PCI.
- Drop undefined concept 'vring'.
- Add 'Virtio-oF'(short for 'Virtio Over Fabrics'), and use this instead.
- Add mapping between target and initiator.
- Add Virtio-oF queue mapping.
- Fix grammar flaws.
[PATCH v2 02/11] transport-fabrics: introduce Virtio Qualified Name
- Use 'NUL' instead of 'NULL'.
- Add 'including the NUL character' in maximum name.
[PATCH v2 03/11] transport-fabircs: introduce Segment Descriptor
[PATCH v2 04/11] transport-fabrics: introduce Stream Transmission
[PATCH v2 05/11] transport-fabrics: introduce Keyed Transmission
- Merge three patches into one.
- Rename this section to 'Virtio-oF Protocol Data Unit' instead of 'Transmission Protocol'.
- Remove undefined 'opcode' reference.
- Drop common 'struct virtio_of_vring_desc'
- For stream data transfers, use a single command/completion instead of descriptors.
- For keyed data transport, use a single descriptor instead of multi descriptors. Also support keyed descriptor count probe.
[PATCH v2 06/11] transport-fabrics: introduce command set
[PATCH v2 07/11] transport-fabrics: introduce opcodes
[PATCH v2 08/11] transport-fabrics: introduce status of completion
- Merge three patches into one.
- Drop common data structures definition, define data structure for each command.
- Drop virtio_of_op_get_num_queues, the Virtio-oF device instance would response error status on invalid virtqueue.
- Allow Virtio-oF virtqueue to use empty connect body.
- Allow Virtio-oF virtqueue to specify queue size on connecting.
- Drop errno like status, define detailed status.
- Other minor fixes.
[PATCH v2 09/11] transport-fabrics: add TCP&RDMA binding
- Rename TCP to TCP/IP to avoid ambiguity.
- Add TLS TCP/IP transport.
- Add RDMA opcode usage.
[PATCH v2 10/11] transport-fabrics: add device initialization
- Drop PCI reference, describe device initialization instead.
- Fix grammar flaws.
[PATCH v2 11/11] transport-fabrics: support inline data for keyed
- Use eager buffer instead.
v1 -> v2:
- Suggested by Parav, split a large patch into several small patches.
- Small changes for VQN, add "There is no strict style limitation".
- Move *bytes* field limitation from get/set config opcode section to
Config Command.
v1:
Introduce Virtio-oF specification, include:
- overview
- Virtio Qualified Name
- Segment Descriptor definition
- Buffer Mapping definition: Stream Transmission and Keyed Transmission
- Command set definition
- opcode definition
- status definition
- transport binding: TCP and RDMA
- device initialization
Previous discussion:
https://lists.oasis-open.org/archives/virtio-comment/202304/msg00442.html
zhenwei pi (7):
transport-fabrics: introduce Virtio Over Fabrics overview
transport-fabrics: introduce Virtio-oF Qualified Name
transport-fabrics: introduce Virtio-oF Protocol Data Unit
transport-fabrics: introduce command set
transport-fabrics: introduce transport binding
transport-fabrics: add device initialization
transport-fabrics: introduce keyed eager buffers
content.tex | 1 +
transport-fabrics.tex | 881 ++++++++++++++++++++++++++++++++++++++++++
2 files changed, 882 insertions(+)
create mode 100644 transport-fabrics.tex
--
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/
next reply other threads:[~2023-06-19 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 8:31 zhenwei pi [this message]
2023-06-19 8:31 ` [virtio-comment] [PATCH v3 1/7] transport-fabrics: introduce Virtio Over Fabrics overview zhenwei pi
2023-06-19 8:31 ` [virtio-comment] [PATCH v3 2/7] transport-fabrics: introduce Virtio-oF Qualified Name zhenwei pi
2023-06-19 8:31 ` [virtio-comment] [PATCH v3 3/7] transport-fabrics: introduce Virtio-oF Protocol Data Unit zhenwei pi
2023-06-19 8:31 ` [virtio-comment] [PATCH v3 4/7] transport-fabrics: introduce command set zhenwei pi
2023-06-19 8:31 ` [virtio-comment] [PATCH v3 5/7] transport-fabrics: introduce transport binding zhenwei pi
2023-06-19 8:31 ` [virtio-comment] [PATCH v3 6/7] transport-fabrics: add device initialization zhenwei pi
2023-06-19 8:31 ` [virtio-comment] [PATCH v3 7/7] transport-fabrics: introduce keyed eager buffers zhenwei pi
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=20230619083131.1544999-1-pizhenwei@bytedance.com \
--to=pizhenwei@bytedance.com \
--cc=helei.sig11@bytedance.com \
--cc=houp@yusur.tech \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=stefanha@redhat.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).