On Thu, Mar 1, 2012 at 9:01 AM, Amos Kong <ak...@redhat.com> wrote: > This patch makes the kvm_io_range array can be resized dynamically. > Set an upper bounds for kvm_io_range to limit userspace. > 1000 is a very large limit and not bloat the typical user.
Whats the reason for making everything dynamic? Memory savings there aren't that significant. If you want to make it more efficient just define: static struct kvm_io_bus io_bus[2]; somewhere in kvm_main.c, and just switch between them when you need to do insertion and removal of devices. You get the benefit of zero slub usage, no allocations in any of the paths, and much simpler logic. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
