Dear Mooney I've read the libvirt pqos feature spec[1] that you shared during the weekly meeting. I want to understand correctly why the development on this feature is currently stalled, and I would appreciate community feedbacks on the best approach for supporting RDT/MPAM. 1. My understanding of the libvirt pqos feature proposal The current libvirt pqos specification[1] is not designed that CPUs can be assigned to specific cache banks. To resolve an above problem, improving the libvirt pqos spec will be restarted if the feature of NUMA topology with resource providers[2] is complete. However, significant refactoring in placement is currently constrained because placement has scalability problems[3]. Nova community is actively addressing them. Is my understanding correct? Please point out any misunderstandings. Any comments or clarifications would also be appreciated. 2. Which solution for supporting RDT/MPAM feature is the best to communities I think the optimal solution involves resolving scalability problems[3], accelerating development of NUMA topology with RPs[2] and the libvirt pqos feature[1]. However, I assume this will take considerable time(5-6cycles?). Therefore, I would like to confirm whether proposing a new design without resource providers (e.g., developing NUMA topology and pqos feature within nova[4]) would be an acceptable alternative. [1] https://review.opendev.org/c/openstack/nova-specs/+/662264/1 [2] https://review.opendev.org/c/openstack/nova-specs/+/728009 [3] https://review.opendev.org/c/openstack/nova-specs/+/938070 [4] https://review.opendev.org/q/topic:%22bp/libvirt-smarter-cpu-placement%22 Regards, Taketani