[Starlingx-discuss] Pending: Support single huge page size for openstack worker node

[Liu, Tao]

Hi All,

The changes to support  single huge page size have been merged into master.

In this first update, the auto-provision of VM huge pages has been changed from 2M to 1G.

A subsequent update,  will remove the auto-provisioning of huge pages for both VM and vSwitch.
If any test case is dependent on the default VM huge pages,  a new step will be required to allocate huge pages for VM on a openstack worker node.
Prior to unlocking a worker node , user provisioning of the vSwitch memory would be required,  if vswitch_type is set to OVS-DPDK.

Regards,
Tao

From: Liu, Tao
Sent: Thursday, August 15, 2019 1:06 PM
To: starlingx-discuss at lists.starlingx.io
Subject: Pending: Support single huge page size for openstack worker node

Hi All,

Per story 2006295<https://storyboard.openstack.org/#!/story/2006295>, we are in the process of supporting single huge page size for openstack worker node.  This means we will enforce the provisioning of a single huge page size
per worker, which aligns with the non-openstack worker behavior.   The automated test cases that attempt to allocate both 2M and 1G huge pages on a worker node should be updated.

The code changes are available here:
https://review.opendev.org/#/c/676710/


Regards,

Tao Liu, Member of Technical Staff, Engineering,, Wind River
direct 613.963.1413 fax: 613.492.7870 skype: tao_at_home
350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190821/95c7de36/attachment.html>