Re: [PATCH 3/5] vhost: support upto 509 memory regions
From: Michael S. Tsirkin
Date: Wed Jun 17 2015 - 12:41:46 EST
On Wed, Jun 17, 2015 at 06:38:25PM +0200, Paolo Bonzini wrote:
> On 17/06/2015 18:34, Michael S. Tsirkin wrote:
> > On Wed, Jun 17, 2015 at 06:31:32PM +0200, Paolo Bonzini wrote:
> >> On 17/06/2015 18:30, Michael S. Tsirkin wrote:
> >>> Meanwhile old tools are vulnerable to OOM attacks.
> >> For each vhost device there will be likely one tap interface, and I
> >> suspect that it takes way, way more than 16KB of memory.
> > That's not true. We have a vhost device per queue, all queues
> > are part of a single tap device.
> s/tap/VCPU/ then. A KVM VCPU also takes more than 16KB of memory.
That's up to you as a kvm maintainer :)
People are already concerned about vhost device
memory usage, I'm not happy to define our user/kernel interface
in a way that forces even more memory to be used up.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/