pinggit
commented
3 years ago “NIC connected to vrouter (either physical or virtual) can be configured to several queues”. I understand the vNIC part. Not only. This is what I’ve tried to explain. Concerning the number of queues configured on vNIC, it is handled by Nova.
Does it apply for pNIC also? Yes. The number of queues configured on pNIC is handled by the vRouter using the DPDK libraries. vRouter is configuring a many queues as the number of vRouter cores it has been allocated to with CPU_LIST parameter.
Can I configure single-queue or multi-queue for , say, intel NIC? How about bond? vRouter does not really see each individual NIC. In fact, using DPDK library the vrouter is building a single pNIC = bond. This is this entity which is created with DPDK, and this entity is configured with as many queues as the number of vrouter cores.
Do not forget that queues created there are done by DPDK vrouter application or Nova. They are not the physical queues that are actually on the pNIC. You have a first step that consist to take all packets arriving in physical queues, then apply a RSS hash, and using the result to spread them in DPDK queues. This task is done in background by DPDK (using DMA) and is transparent for the application. The DPDK application is only seeing the representation of the physical card across the DPDK queue it has been requested to create (this is EAL = Ethernet Abstraction Layer a representation made in compute memory which is mapped on the real physical card)
I hope this is more clear. Maybe we will have to add such an explanation to the book.
Laurent
“NIC connected to vrouter (either physical or virtual) can be configured to several queues”. I understand the vNIC part. Does it apply for pNIC also? Can I configure single-queue or multi-queue for , say, intel NIC? How about bond?
similar to #2