Earlier  
Posted Nick Remark
#openstack-nova - 2020-07-08
14:04:41 sean-k-mooney well they woudl only have different based_frequency if the polcy was enabled
14:04:47 sean-k-mooney by defualt they would all have the same
14:05:17 sean-k-mooney or are you saying when we turn this on in the bios they go to different base frequencies and we can select the frequency
14:05:18 huaqiang yes
14:05:48 huaqiang the unit of 'base_frequency' is Mhz, you just read the CPU frequency
14:06:19 huaqiang do you know, in new platform ,we have another SST
14:06:29 huaqiang the SST-TF (turbo frequency)
14:06:31 sean-k-mooney three are 4
14:06:45 sean-k-mooney SST-BF adjust base frequency
14:07:05 sean-k-mooney SST-CP adjust the core priport for core power delivery
14:07:13 huaqiang which is better for create two groups of CPUs with high or low turbo frequency
14:07:26 huaqiang turbo frequency is commonly used
14:07:35 sean-k-mooney SST-PP disables cores/enables cores to make more power/theremals avilabel for other cores
14:07:50 huaqiang yes
14:08:02 sean-k-mooney and SST-TB i guess work like SST-BF but allwos different terbo frequecies
14:08:23 huaqiang correct
14:09:07 huaqiang they are enabled in different interfaces
14:09:43 huaqiang so I'd like to let the 3rd-part tool for enabling it
14:09:48 sean-k-mooney https://github.com/intel/CommsPowerManagement/blob/master/sst_bf.py has code for some of the flavor of SST
14:10:05 huaqiang it's for SST-BF
14:10:31 sean-k-mooney yes although i tought there was code maybe in andiffer file for the other ones
14:10:55 huaqiang I don't find it
14:11:45 huaqiang PP and BF are ready in the silicon of last year
14:12:10 huaqiang TF is new, it is enabled on this year's product
14:12:33 sean-k-mooney yep CP should be there too in existing silicon
14:12:38 sean-k-mooney https://github.com/intel/CommsPowerManagement/blob/97c151ac2649535ad0d51113883a96764d9c7b87/pwr/setup.py#L15
14:12:40 huaqiang CP is also launched
14:12:42 huaqiang in last year
14:12:49 huaqiang yes
14:12:52 sean-k-mooney they reference SST-CP in the metadata
14:13:05 openstackgerrit Stephen Finucane proposed openstack/nova master: crypto: Add type hints https://review.opendev.org/739207
14:13:05 sean-k-mooney so i suspec ti senabled in one of the files
14:13:05 openstackgerrit Stephen Finucane proposed openstack/nova master: virt: Add 'context', drop 'network_info' parameters for 'unrescue' https://review.opendev.org/730382
14:13:06 openstackgerrit Stephen Finucane proposed openstack/nova master: libvirt: Add vTPM config support https://review.opendev.org/739209
14:13:06 openstackgerrit Stephen Finucane proposed openstack/nova master: libvirt: Split '_create_domain' function https://review.opendev.org/739208
14:13:07 openstackgerrit Stephen Finucane proposed openstack/nova master: crypto: Add support for creating, destroying vTPM secrets https://review.opendev.org/739211
14:13:07 openstackgerrit Stephen Finucane proposed openstack/nova master: scheduler: Request vTPM trait based on flavor or image https://review.opendev.org/739210
14:13:08 openstackgerrit Stephen Finucane proposed openstack/nova master: manager: Prevent compute startup on invalid vTPM config https://review.opendev.org/739212
14:13:09 openstackgerrit Stephen Finucane proposed openstack/nova master: Add support for resize and cold migration of emulated TPM files https://review.opendev.org/639934
14:13:09 openstackgerrit Stephen Finucane proposed openstack/nova master: docs: Add docs for vTPM support https://review.opendev.org/739213
14:13:09 openstackgerrit Stephen Finucane proposed openstack/nova master: Add emulated TPM support to Nova https://review.opendev.org/631363
14:13:10 openstackgerrit Stephen Finucane proposed openstack/nova master: utils: Move 'get_bdm_image_metadata' to nova.block_device https://review.opendev.org/739996
14:14:22 huaqiang It's better to have them
14:17:48 sean-k-mooney i found this before https://github.com/intel/sst-bf-openstack-setup-automation which tries to automate it but it was not entirely trival to figure out what it was doing with our painstakingly reverse engienriing it
14:18:44 sean-k-mooney huaqiang: its currently the best reference i coudl find however
14:19:05 sean-k-mooney it also only really covers SST-BF
14:22:19 alex_xu gibi: tony su is on the same team with me
14:22:38 huaqiang sean-k-mooney, OVS is a good workload for BF
14:23:37 sean-k-mooney huaqiang: ovs-dpdk even more so because you can trivialy pin the PMDs
14:24:12 sean-k-mooney kernel ovs is tricker since some of the processing is also done in the vhost_threads wo ideally you want toes to also be on the high priority cores
14:24:48 sean-k-mooney thos are kernel thready however that are spawned in responce to qemu so im not sure its easy to do that
14:25:09 alex_xu gibi: oh...just saw huaqiang already help on that
14:25:12 sean-k-mooney for ovs-dpdk however all the packet procesing is done in the pmd so its easy to configure
14:28:29 huaqiang we can use mixed instance and dedicated cores for PMD threads, and shared cores for other threads, right
14:28:31 huaqiang ?
14:29:19 gibi alex_xu: yes, thanks
14:30:23 huaqiang Hie alex_xu, stephenfin, the mixed instance pathces are ready for next review, please review at your convenient time!
14:30:50 alex_xu huaqiang: got it!
14:31:01 huaqiang alex_xu thanks!
14:31:19 alex_xu np
14:40:14 sean-k-mooney huaqiang: partly yes but i dont belive the core affitiy we apply to the vm cpus applyse to the kernel thread spwaned by the vhost kernel module
14:40:46 sean-k-mooney the are not forked or spwaned from the process
14:41:16 sean-k-mooney so i would not assume any cgroup/taskset limits applied to the eumlator thread or to the vcpus would have any affect on where they run
14:42:25 sean-k-mooney you could restict the ovs-vsitchd to a set of thread too but again i thikn that woudl only apply to the user spacee process not the kernel threads. it may be its not clear that it would
14:42:34 sean-k-mooney anyway i think this is out of scope of nova
14:45:22 huaqiang can you limit the kernel threads to some CPUs?
14:45:37 huaqiang I know the interrput thread could be pinned
14:46:40 huaqiang any know nova don't have the capability for kernel pinning
14:46:57 huaqiang s/any know/anyway/
14:58:32 openstackgerrit Dan Smith proposed openstack/nova master: DNM: Try to make a glance multistore job https://review.opendev.org/734184
15:00:05 openstackgerrit Andrey Kurilin proposed openstack/python-novaclient master: Switch legacy Zuul jobs to native Zuul v3 jobs https://review.opendev.org/725163
15:30:21 openstackgerrit Merged openstack/nova stable/stein: libvirt: avoid cpu check at s390x arch https://review.opendev.org/701526
15:30:31 openstackgerrit Merged openstack/nova stable/stein: Reserve DISK_GB resource for the image cache https://review.opendev.org/732529
15:30:38 openstackgerrit Merged openstack/nova stable/stein: Add admin doc information about image cache resource accounting https://review.opendev.org/732542
15:30:46 openstackgerrit Merged openstack/nova stable/train: Fix cherry-pick check for merge patch https://review.opendev.org/739177
15:42:25 openstackgerrit Elod Illes proposed openstack/nova stable/stein: Check cherry-pick hashes in pep8 tox target https://review.opendev.org/737922
16:18:01 openstackgerrit Balazs Gibizer proposed openstack/nova master: Document nova in tree virt drivers https://review.opendev.org/740061
16:22:11 openstackgerrit sean mooney proposed openstack/nova stable/train: add [libvirt]/max_queues config option https://review.opendev.org/740064
16:40:06 sean-k-mooney gmann: is there a patch to adress the libffi-dev dep for https://review.opendev.org/#/c/738130/1
16:41:20 sean-k-mooney i could add it a bindeps file for os-vif adn list it i guess but this is needed for any pyton lib that uses the forign function interface lib
16:41:30 sean-k-mooney we dont use it directly its transitive
16:44:36 elod sean-k-mooney: we've just seen the same issue and I think if you change the cffi in lower-constraints.txt to a newer one then that failure won't come
16:45:26 elod sean-k-mooney: since the problem is that cffi is not there in wheels repo
16:45:28 sean-k-mooney i doutb it this is becasue we dont have the cpackage so when we compile it fails to find the header
16:45:36 elod at least 1.11.5
16:45:39 gmann sean-k-mooney elod it should be from bindep but i have not tried the cffi new version
16:45:40 sean-k-mooney changing a pip constratint shoudl not alter that
16:46:07 elod sean-k-mooney: that's why only the lower-constraints job fails and any other passes
16:46:09 sean-k-mooney have they started packaging the c header files for cffi?
16:46:53 sean-k-mooney hum ok
16:47:06 gmann cffi==1.11.5 is current now.
16:47:15 sean-k-mooney well we can raise it i guess but really we shoudl just be installing the header file form the distro
16:47:52 gmann ok, let me update the patch and try
16:48:24 elod cffi=1.14.0 is installed without any problem, see https://zuul.opendev.org/t/openstack/build/b8c5b0f682284567949ba9a0b598f61e/log/tox/py38-1.log#63
16:48:27 sean-k-mooney well we dont have bindeps in os-vif currently are you going to raise the lower-constiat or add a bindep.txt
16:48:43 sean-k-mooney we shoudl add bindep.txt but there are other things we shoudl do in general fo that.
16:50:33 elod of course, adding bindep.txt with all the relevant binary dependency is a good thing :)
16:51:03 gmann yeah bindeps with libffi-dev [platform:dpkg]
16:51:46 elod just wanted to let you know why is the weird behavior (failing with lower-constraints job but not at the other jobs)
16:51:49 elod :)

Earlier   Later