On 10/23/25 1:48 PM, Eelco Chaudron via dev wrote: > Hi all, > > We’d like to bring a design discussion to the community regarding a > requirement > for RX queues from different ports to be grouped on the same PMD. > We’ve had some initial talks with the NVIDIA team (who are CC’d), and I think > this discussion will benefit from upstream feedback and involvement. > > Here is the background and context: > > The goal is to automatically (i.e., without user configuration) group together > the same queue IDs from different, but related, ports. A key use case is an > E-Switch manager (e.g., p0) and its VF representatives (e.g., pf0vf0, pf0vf1).
Could you explain why this is a requirement to poll the same queue ID of different, though related, ports by the same thread? It's not obvious. I suspect, in a typical setup with hardware offload most of the ports will be related this way. > > This new grouping logic must also respect existing scheduling algorithms like > ‘cycles’. For example, if ‘cycles’ is used, the scheduler would need to base > its > decision on the sum of cycles for all RX queues within that group. > > For this, we think we need some kind of netdev API that tells the > rxq_scheduling() > function which port-queues belong to a group. Once this group is known, the > algorithm > can perform the proper calculation on the aggregated group. > > Does this approach sound reasonable? We are very open to other ideas on how to > discover these related queues. > > Kevin, I’ve copied you in, as you did most of the existing implementation, so > any > feedback is appreciated. > > Cheers, > Eelco _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
