From dd1b812ebd0c0d969048acbc1f24432d284772fe Mon Sep 17 00:00:00 2001 From: Wang Huaqiang Date: Fri, 19 Jun 2020 21:02:14 +0800 Subject: [PATCH] release note: add new features introduces by use-pcpu-and-vcpu-in-one-instance Add the release note for bp/use-pcpu-and-vcpu-in-one-instance. Part of blueprint use-pcpu-and-vcpu-in-one-instance Change-Id: I510d7b624d2eb0f9e4e7d07bf1fec4d59a6d2593 Signed-off-by: Wang Huaqiang --- ...vcpu-in-one-instance-0ea66aeb9c2970de.yaml | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 releasenotes/notes/use-pcpu-and-vcpu-in-one-instance-0ea66aeb9c2970de.yaml diff --git a/releasenotes/notes/use-pcpu-and-vcpu-in-one-instance-0ea66aeb9c2970de.yaml b/releasenotes/notes/use-pcpu-and-vcpu-in-one-instance-0ea66aeb9c2970de.yaml new file mode 100644 index 000000000000..5f401bd8b2be --- /dev/null +++ b/releasenotes/notes/use-pcpu-and-vcpu-in-one-instance-0ea66aeb9c2970de.yaml @@ -0,0 +1,22 @@ +--- +features: + - | + Add the ``mixed`` instance CPU allocation policy for instance mixing with + both ``PCPU`` and ``VCPU`` resources. This is useful for applications that + wish to schedule the CPU intensive workload on the ``PCPU`` and the other + workloads on ``VCPU``. The mixed policy avoids the necessity of making + all instance CPUs to be pinned CPUs, as a result, reduces the consuption + of pinned CPUs and increases the instance density. + + Extend the real-time instance with the ``mixed`` CPU allocation policy. In + comparing with ``dedicated`` policy real-time instance, the non-real-time + CPUs are not longer required to be pinned on dedicated host CPUs, but + float on a range of host CPUs sharing with other instances. + - | + Add the extra spec ``hw:cpu_dedicated_mask`` to set the pinned CPUs for + the mixed instance. This is a core mask and can be used to include or + exclude CPUs. Any core not included or explicitly excluded is treated as a + shared CPU. + - | + Export instance pinned CPU list through the ``dedicated_cpus`` section in + the metadata service API.