virtio — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
[PATCH requirements 0/7] virtio net new features requirements
On Fri, Jun 02, 2023 at 01:03:05AM +0300, Parav Pandit wrote:
> Add header data split requirements for the receive packets.
>
> Signed-off-by: Parav Pandit <[email protected]>
> ---
> 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 f94848e..31680b7 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. Receive virtqueue n-tuple steering
> 5. Device timestamp for tx and rx packets
> +6. Header data split for the receive virtqueue
>
> # 3. Requirements
> ## 3.1 Device counters
> @@ -209,3 +210,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).
what is header here? which layer?
> +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
this is a requirement why?
> +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.
weirdly specific.
how does device even know the cache line?
> --
> 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: [email protected]
> Unsubscribe: [email protected]
> List help: [email protected]
> 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/
>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]