From: Parav Pandit <parav@nvidia.com>
To: <virtio-comment@lists.oasis-open.org>
Cc: <shahafs@nvidia.com>, <hengqi@linux.alibaba.com>,
<virtio@lists.oasis-open.org>, Parav Pandit <parav@nvidia.com>
Subject: [virtio-comment] [PATCH REQUIREMENTS v1 7/7] net-features: Add header data split requirements
Date: Wed, 14 Jun 2023 07:22:57 +0300 [thread overview]
Message-ID: <20230614042257.1252775-8-parav@nvidia.com> (raw)
In-Reply-To: <20230614042257.1252775-1-parav@nvidia.com>
Add header data split requirements for the receive packets.
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
net-workstream/features-1.4.md | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/net-workstream/features-1.4.md b/net-workstream/features-1.4.md
index 2b51759..f26b61c 100644
--- a/net-workstream/features-1.4.md
+++ b/net-workstream/features-1.4.md
@@ -11,6 +11,7 @@ together is desired while updating the virtio net interface.
3. Virtqueue notification coalescing re-arming support
4 Virtqueue receive flow filters (RFF)
5. Device timestamp for tx and rx packets
+6. Header data split for the receive virtqueue
# 3. Requirements
## 3.1 Device counters
@@ -228,3 +229,15 @@ struct vnet_rx_completion {
point of reception from the network.
3. The device should provide a receive packet timestamp in a single DMA
transaction along with the rest of the receive completion fields.
+
+## 3.6 Header data split for the receive virtqueue
+1. The device should be able to DMA the packet header and data to two different
+ memory locations, this enables driver and networking stack to perform zero
+ copy to application buffer(s).
+2. The driver should be able to configure maximum header buffer size per
+ virtqueue.
+3. The header buffer to be in a physically contiguous memory per virtqueue
+4. The device should be able to indicate header data split in the receive
+ completion.
+5. The device should be able to zero pad the header buffer when the received
+ header is shorter than cpu cache line size.
--
2.26.2
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/
prev parent reply other threads:[~2023-06-14 4:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 4:22 [virtio-comment] [PATCH REQUIREMENTS v1 0/7] virtio net new features requirements Parav Pandit
2023-06-14 4:22 ` [virtio-comment] [PATCH REQUIREMENTS v1 1/7] net-features: Add requirements document for release 1.4 Parav Pandit
2023-06-14 4:22 ` [virtio-comment] [PATCH REQUIREMENTS v1 2/7] net-features: Add low latency transmit queue requirements Parav Pandit
2023-06-14 4:22 ` [virtio-comment] [PATCH REQUIREMENTS v1 3/7] net-features: Add low latency receive " Parav Pandit
2023-06-14 4:22 ` [virtio-comment] [PATCH REQUIREMENTS v1 4/7] net-features: Add notification coalescing requirements Parav Pandit
2023-06-14 4:22 ` [virtio-comment] [PATCH REQUIREMENTS v1 5/7] net-features: Add n-tuple receive flow filters requirements Parav Pandit
2023-06-14 4:22 ` [virtio-comment] [PATCH REQUIREMENTS v1 6/7] net-features: Add packet timestamp requirements Parav Pandit
2023-06-14 4:22 ` Parav Pandit [this message]
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=20230614042257.1252775-8-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=hengqi@linux.alibaba.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio@lists.oasis-open.org \
/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).