)]}'
{"specs/mitaka/approved/virt-driver-cpu-pinning.rst":[{"author":{"_account_id":8768,"name":"Chris Friesen","email":"chris.friesen@windriver.com","username":"cbf123"},"change_message_id":"dc2feb2c5419e372a26f293fb6b405b368aa4fc7","unresolved":false,"context_lines":[{"line_number":63,"context_line":"   different core and no vCPUs from other guests will be able to be"},{"line_number":64,"context_line":"   placed on the same core. ie one thread sibling is guaranteed to"},{"line_number":65,"context_line":"   always be unused,"},{"line_number":66,"context_line":" - require: if the host has threads, vCPU will be placed on the same"},{"line_number":67,"context_line":"   core, so they are thread siblings."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"The image metadata properties will also allow specification of the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa80f949_fea2b14a","line":66,"updated":"2015-11-04 17:25:09.000000000","message":"I think this should be something like:\n\n- require: the scheduler will not place the guest on a host which does not have hyperthreads, and vCPUs will be placed on the thread siblings of a single core.  This implies that you cannot have more vCPUs in the guest than the number of thread siblings on a single core on the host.","commit_id":"9b84d6a733560aef5fe769315ea73e9b803c9136"},{"author":{"_account_id":8768,"name":"Chris Friesen","email":"chris.friesen@windriver.com","username":"cbf123"},"change_message_id":"d2c20fa7e057f8f19a9299183fc0e978fe01825f","unresolved":false,"context_lines":[{"line_number":63,"context_line":"   different core and no vCPUs from other guests will be able to be"},{"line_number":64,"context_line":"   placed on the same core. ie one thread sibling is guaranteed to"},{"line_number":65,"context_line":"   always be unused,"},{"line_number":66,"context_line":" - require: if the host has threads, vCPU will be placed on the same"},{"line_number":67,"context_line":"   core, so they are thread siblings."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"The image metadata properties will also allow specification of the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa80f949_8ad798ec","line":66,"in_reply_to":"fa80f949_be2189b6","updated":"2015-11-04 20:31:59.000000000","message":"I\u0027m guessing you mean something like this?\n\nhttps://review.openstack.org/#/c/241751/1","commit_id":"9b84d6a733560aef5fe769315ea73e9b803c9136"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"e3d1c53cb9aa1a004da09629461b20adb78a4fdb","unresolved":false,"context_lines":[{"line_number":63,"context_line":"   different core and no vCPUs from other guests will be able to be"},{"line_number":64,"context_line":"   placed on the same core. ie one thread sibling is guaranteed to"},{"line_number":65,"context_line":"   always be unused,"},{"line_number":66,"context_line":" - require: if the host has threads, vCPU will be placed on the same"},{"line_number":67,"context_line":"   core, so they are thread siblings."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"The image metadata properties will also allow specification of the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa80f949_be2189b6","line":66,"in_reply_to":"fa80f949_fea2b14a","updated":"2015-11-04 17:27:54.000000000","message":"we can take this to a follow up patch, given we merged this before.","commit_id":"9b84d6a733560aef5fe769315ea73e9b803c9136"}]}