[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [PATCH REQUIREMENTS v1 4/7] net-features: Add notification coalescing requirements
Add virtio net device notification coalescing improvements requirements. Signed-off-by: Parav Pandit <parav@nvidia.com> --- changelog: v0->v1: - updated the description --- net-workstream/features-1.4.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/net-workstream/features-1.4.md b/net-workstream/features-1.4.md index 3e8b5a4..a34556c 100644 --- a/net-workstream/features-1.4.md +++ b/net-workstream/features-1.4.md @@ -8,6 +8,7 @@ together is desired while updating the virtio net interface. # 2. Summary 1. Device counters visible to the driver 2. Low latency tx and rx virtqueues for PCI transport +3. Virtqueue notification coalescing re-arming support # 3. Requirements ## 3.1 Device counters @@ -157,3 +158,14 @@ struct vnet_rx_completion { which can be recycled by the driver when the packets from the completed page is fully consumed. 8. The device should be able to consume multiple pages for a receive GSO stream. + +## 3.3 Virtqueue notification coalescing re-enable support +0. Design goal: + a. Avoid constant notification from the device even in conditions when + the driver may not have acted on the previous pending notification. +1. When Tx and Rx virtqueue notification coalescing is enabled, and when such + notification is reported by the device, device should be able to disable + further notifications until the driver finish reacting to the already + generated notification. +2. When the driver enables the notification coalescing reporting, the device + to notify again if notification coalescing conditions are met. -- 2.26.2
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]