[openstack-dev] [Neutron] One performance issue about VXLAN pool initiation

Carl Baldwin carl at ecbaldwin.net
Thu Jun 26 19:59:10 UTC 2014

++.  This might also be useful in ipam.

I'll have a look at the patch regardless for the short term.  (I had
actually suggested something similar on Eugene's patch review.)

On Jun 26, 2014 8:14 AM, "Zang MingJie" <zealot0630 at gmail.com> wrote:

> it would be better to make the range increase dynamic, instead of create
> all entries at initialize.
> for example, if vxlan range 1~1M is configured, only initialize 1~1K, when
> it has been used up, extend the range to 1K~2K, and so on.
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140626/1844dd16/attachment.html>

More information about the OpenStack-dev mailing list