Profile

? 2024/1/30 ??4:27, Parav Pandit ??: >> From: Heng Qi >> Sent: Tuesday, January 30, 2024 12:06 PM >> >> ? 2024/1/30 ??2:05, Parav Pandit ??: >>> Hi Heng, >>> >>>> From: Heng Qi >>>> Sent: Tuesday, January 30, 2024 10:15 AM >>>> To: virtio-comment@lists.oasis-open.org >>>> Cc: ...

? 2024/1/30 ??2:05, Parav Pandit ??: > Hi Heng, > >> From: Heng Qi >> Sent: Tuesday, January 30, 2024 10:15 AM >> To: virtio-comment@lists.oasis-open.org >> Cc: Jason Wang ; Michael S. Tsirkin >> ; Xuan Zhuo ; Parav Pandit >> >> Subject: [PATCH v3] virtio-net: support setting ...

Currently, when each time the driver attempts to update the coalescing parameters for a vq, it needs to kick the device and wait for the ctrlq response to return. The following path is observed: 1. Driver kicks the device; 2. After the device receives the kick, CPU scheduling occurs and DMA multiple ...

å 2024/1/24 äå7:15, Michael S. Tsirkin åé: This is not a huge deal since it's a SHOULD anyway, so make the new requirement SHOULD too. Signed-off-by: Michael S. Tsirkin --- device-types/net/description.tex 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/device-types/net/description.tex ...

Currently, when each time the driver attempts to update the coalescing parameters for a vq, it needs to kick the device and wait for the ctrlq response to return. The following path is observed: 1. Driver kicks the device; 2. After the device receives the kick, CPU scheduling occurs and DMA multiple ...