19/11/2026 19:41, Luca Vizzarro:
> Hi Koushik,
> 
> thank you for this. Accepted to next-dts with minor doc changes.
> 
> Luca
> 

I've pulled it in main,
but my AI raises multiple warnings:

- With the chained port list [0, 2, 1], reverse traffic bypasses virtio
  but contributes to aggregate throughput, allowing false passes.

- Virtio-user defaults to 256 descriptors:
  setting testpmd’s ring sizes does not replace the missing queue_size vdev 
parameter.

- The queues=2 case leaves testpmd using one Rx/Tx queue;
  rx_queues and tx_queues must also be set.

- allowed_ports=[] bypasses DTS’s configured port selection,
  making the assumed port numbering unreliable.

- Hardcoded core IDs ignore DTS’s configured CPU selection.

- The packed vectorized case can silently fall back to scalar processing;
  the selected datapath should be verified.

- In the vhost suite, virtio’s two requested forwarding cores are reduced to one
  because it has only one forwarding stream.


Reply via email to