Dear DPDK Team,

I hope this email finds you well. 

I'm writing to inquire about DPDK's future plans regarding dynamic CPU initialization support, particularly in Kubernetes environments where exclusive CPU Pod scaling is being enhanced.

Backgroud:
With Kubernetes upcoming improvements to InPlacePodVerticalScaling for exclusive CPU Pods (Guaranteed QoS Pods), we have encountered a limitation when using DPDK:

• A Pod initialized with 5 exclusive CPUs can have DPDK’s EAL successfully bind and utilize these cores.
• However, when the Pod scales up (e.g., adding 2 new CPUs), DPDK currently lacks native mechanisms to detect and initialize the newly allocated cores. This forces us to either restart the Pod (causing service disruption) or leave additional CPUs underutilized.

Key Questions:

1. Is there an active DPDK roadmap item to support binded and initialized CPUs scaling up and down?
2. If not, would the DPDK community consider contributions in this area, especially given Kubernetes’ evolving CPU management capabilities?

We believe such functionality would significantly benefit cloud-native NFV workloads. Any guidance or references to ongoing work would be greatly appreciated.

Reference Link:

        InPlacePodVerticalScaling Enhancements for guaranteed pods: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/1287-in-place-update-pod-resources/README.md#future-enhancements

        A PR to implement guaranteed pods resize: https://github.com/kubernetes/kubernetes/pull/129719

Thank you for your time and expertise. Looking forward to your insights.

Best regards