[Starlingx-discuss] PCI Interrupt affinity task
Liu, ZhipengS
zhipengs.liu at intel.com
Mon Mar 4 02:34:24 UTC 2019
Hi Jim and all,
I have submitted all my patches for PCI Interrupt affinity feature as below link.
https://review.openstack.org/#/c/640264/
https://review.openstack.org/#/c/640263/
Below one is the patch for removing pci-irq-affinity function from nova.
https://github.com/hustlzp1981/stx-nova/commit/c52432b3e7a240817a2de06321a2459f4862ab6a
Your comments are appreciated!
Thanks!
Zhipeng
From: Gauld, James [mailto:James.Gauld at windriver.com]
Sent: 2019年2月26日 22:07
To: Liu, ZhipengS <zhipengs.liu at intel.com>; starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] PCI Interrupt affinity task
Zhipeng,
Option 1) is a reasonable choice. I agree with your reasoning.
FYI, I don’t think we depend on nova-sriov script anymore, but we haven't actually tested with that removed.
Please add me to your code inspection.
-Jim
From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com]
Sent: February-21-19 10:24 PM
To: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>
Subject: [Starlingx-discuss] PCI Interrupt affinity task
Hi all
Recently, I have being working on pci interrupt affinity task (https://storyboard.openstack.org/#!/story/2004600)
So far I have finished coding, basic deployment test and function test.
Now, I’m preparing for uploading my patch for code review.
However, I need to decide where to put code folder.
>From my point, there are two options below.
1) stx-integ/utilities/nova-utils/pci-affinity-agent
2) stx-config/sysinv/pci-affinity-agent (I put code here currently)
I prefer option 1 as nova-utils is just used to install nova-sriov script only and pci affinity is also an extended feature for nova.
We can reuse nova-utils package with additional RPM for pci-affinity-agent
Any comment from you? Thanks!
zhipeng
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190304/94f698d4/attachment.html>
More information about the Starlingx-discuss
mailing list