<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2018-04-19 10:38 GMT+02:00 Balázs Gibizer <span dir="ltr"><<a href="mailto:balazs.gibizer@ericsson.com" target="_blank">balazs.gibizer@ericsson.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
On Thu, Apr 19, 2018 at 12:45 AM, Eric Fried <openstack@fried.cc> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 I have a feeling we're just going to go back and forth on this, as we<br>
 have for weeks now, and not reach any conclusion that is satisfactory to<br>
 everyone. And we'll delay, yet again, getting functionality into this<br>
 release that serves 90% of use cases because we are obsessing over the<br>
 0.01% of use cases that may pop up later.<br>
</blockquote>
<br>
So I vote that, for the Rocky iteration of the granular spec, we add a<br>
single `proximity={isolate|any}` qparam, required when any numbered<br>
request groups are specified.  I believe this allows us to satisfy the<br>
two NUMA use cases we care most about: "forced sharding" and "any fit".<br>
And as you demonstrated, it leaves the way open for finer-grained and<br>
more powerful semantics to be added in the future.<br>
</blockquote>
<br></span>
Can the proximity param specify relationship between the un-numbered and the numbered groups as well or only between numbered groups?<br>
Besides that I'm +1 about proxyimity={isolate|any}<br>
<br></blockquote><div><br></div><div>What's the default behaviour if we aren't providing the proximity qparam ? Isolate or any ?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Cheers,<br>
gibi<div class="HOEnZb"><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
-efried<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</blockquote>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></div></blockquote></div><br></div></div>