<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<STYLE type=text/css> <!--@import url(scrollbar.css); --></STYLE>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<STYLE> body{FONT-SIZE:12pt; FONT-FAMILY:宋体,serif;} </STYLE>
<META name=GENERATOR content="MSHTML 8.00.7600.16385"><BASE
target=_blank></HEAD>
<BODY
style="LINE-HEIGHT: 1.3; BORDER-RIGHT-WIDTH: 0px; MARGIN: 12px; BORDER-TOP-WIDTH: 0px; BORDER-BOTTOM-WIDTH: 0px; BORDER-LEFT-WIDTH: 0px"
marginheight="0" marginwidth="0">
<DIV><FONT color=#000000 size=3 face=宋体>
<DIV>Hi Liuji, </DIV>
<DIV> </DIV>
<DIV>I'm the owner of
bp support-libvirt-vcpu-topology, </DIV>
<DIV>There are four main reasons that I did not continue to work on it: </DIV>
<DIV>1. the design proposal has not confirmed by core developers of nova </DIV>
<DIV>2. this bp is not accepted in Icehouse development stage </DIV>
<DIV>3. Daniel
expects that this bp should consider together with the other one numa-aware-cpu-binding, but I have no idea to do this for now </DIV>
<DIV>4. I have no enough time to do this at this moment </DIV></FONT></DIV>
<DIV> </DIV>
<DIV align=left><FONT color=#c0c0c0 size=2 face=Verdana>2014-03-05</FONT></DIV>
<DIV align=left><FONT size=2 face=Verdana>
<HR style="WIDTH: 122px; HEIGHT: 2px" id=SignNameHR align=left SIZE=2>
</FONT></DIV>
<DIV align=left><FONT color=#c0c0c0 size=2 face=Verdana><SPAN
id=_FlashSignName>Wangpan</SPAN></FONT></DIV>
<DIV><FONT size=2 face=Verdana>
<HR>
</FONT></DIV>
<DIV><FONT size=2 face=Verdana><STRONG>发件人：</STRONG>"Liuji (Jeremy)"
<jeremy.liu@huawei.com></FONT></DIV>
<DIV><FONT size=2
face=Verdana><STRONG>发送时间：</STRONG>2014-03-05 15:02</FONT></DIV>
<DIV><FONT size=2 face=Verdana><STRONG>主题：</STRONG>Re: [openstack-dev] [nova]
Questions about guest NUMA and memory binding policies</FONT></DIV>
<DIV><FONT size=2 face=Verdana><STRONG>收件人：</STRONG>"OpenStack Development
Mailing List (not for usage
questions)"<openstack-dev@lists.openstack.org></FONT></DIV>
<DIV><FONT size=2 face=Verdana><STRONG>抄送：</STRONG>"Luohao
\(brian\)"<brian.luohao@huawei.com>,"Yuanjing
\(D\)"<yj.yuan@huawei.com></FONT></DIV>
<DIV><FONT size=2 face=Verdana></FONT> </DIV>
<DIV><FONT size=2 face=Verdana>
<DIV>Hi Steve, </DIV>
<DIV> </DIV>
<DIV>Thanks for your reply. </DIV>
<DIV> </DIV>
<DIV>I didn't know why the blueprint numa-aware-cpu-binding seems to have no more progress until read the two mails mentioned in your mail. </DIV>
<DIV> </DIV>
<DIV>The use case analysis in the mails are very clear, they are also what I concern about. </DIV>
<DIV>I agree that we shouldn't provide pCPU/vCPU mapping for the ending user and how to provide them for the user need more consideration. </DIV>
<DIV> </DIV>
<DIV>The use cases I concern more are the pCPU's exclusively use(pCPU:vCPU=1:1) and the guest numa. </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Thanks, </DIV>
<DIV>Jeremy Liu </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>> -----Original Message----- </DIV>
<DIV>> From: Steve Gordon [mailto:sgordon@redhat.com] </DIV>
<DIV>> Sent: Tuesday, March 04, 2014 10:29 AM </DIV>
<DIV>> To: OpenStack Development Mailing List (not for usage questions) </DIV>
<DIV>> Cc: Luohao (brian); Yuanjing (D) </DIV>
<DIV>> Subject: Re: [openstack-dev] [nova] Questions about guest NUMA and memory </DIV>
<DIV>> binding policies </DIV>
<DIV>> </DIV>
<DIV>> ----- Original Message ----- </DIV>
<DIV>> > Hi, all </DIV>
<DIV>> > </DIV>
<DIV>> > I search the current blueprints and old mails in the mail list, but </DIV>
<DIV>> > find nothing about Guest NUMA and setting memory binding policies. </DIV>
<DIV>> > I just find a blueprint about vcpu topology and a blueprint about CPU </DIV>
<DIV>> > binding. </DIV>
<DIV>> > </DIV>
<DIV>> > https://blueprints.launchpad.net/nova/+spec/support-libvirt-vcpu-topol </DIV>
<DIV>> > ogy https://blueprints.launchpad.net/nova/+spec/numa-aware-cpu-binding </DIV>
<DIV>> > </DIV>
<DIV>> > Is there any plan for the guest NUMA and memory binding policies setting? </DIV>
<DIV>> > </DIV>
<DIV>> > Thanks, </DIV>
<DIV>> > Jeremy Liu </DIV>
<DIV>> </DIV>
<DIV>> Hi Jeremy, </DIV>
<DIV>> </DIV>
<DIV>> As you've discovered there have been a few attempts at getting some work </DIV>
<DIV>> started in this area. Dan Berrange outlined some of the possibilities in this area </DIV>
<DIV>> in a previous mailing list post [1] though it's multi-faceted, there are a lot of </DIV>
<DIV>> different ways to break it down. If you dig into the details you will note that the </DIV>
<DIV>> support-libvirt-vcpu-topology blueprint in particular got a fair way along but </DIV>
<DIV>> there were some concerns noted in the code reviews and on the list [2] around </DIV>
<DIV>> the design. </DIV>
<DIV>> </DIV>
<DIV>> It seems like this is an area that there is a decent amount of interest in and we </DIV>
<DIV>> should work on list to flesh out a design proposal, ideally this would be </DIV>
<DIV>> presented for further discussion at the Juno design summit. What are your </DIV>
<DIV>> particular needs/desires from a NUMA aware nova scheduler? </DIV>
<DIV>> </DIV>
<DIV>> Thanks, </DIV>
<DIV>> </DIV>
<DIV>> Steve </DIV>
<DIV>> </DIV>
<DIV>> [1] </DIV>
<DIV>> http://lists.openstack.org/pipermail/openstack-dev/2013-November/019715.h </DIV>
<DIV>> tml </DIV>
<DIV>> [2] </DIV>
<DIV>> http://lists.openstack.org/pipermail/openstack-dev/2013-December/022940.h </DIV>
<DIV>> tml </DIV>
<DIV>> </DIV>
<DIV>> _______________________________________________ </DIV>
<DIV>> OpenStack-dev mailing list </DIV>
<DIV>> OpenStack-dev@lists.openstack.org </DIV>
<DIV>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev </DIV>
<DIV> </DIV>
<DIV>_______________________________________________ </DIV>
<DIV>OpenStack-dev mailing list </DIV>
<DIV>OpenStack-dev@lists.openstack.org </DIV>
<DIV>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev </DIV></FONT></DIV></BODY></HTML>