From: Sasha Levin <sasha.levin@oracle.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Sasha Levin <sasha.levin@oracle.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Will Deacon <will.deacon@arm.com>,
kvm@vger.kernel.org, penberg@kernel.org, marc.zyngier@arm.com
Subject: Re: virtio-net mq vq initialization
Date: Mon, 22 Apr 2013 14:32:56 -0400 [thread overview]
Message-ID: <51758258.4010507@oracle.com> (raw)
In-Reply-To: <516B9706.2040601@redhat.com>
On 04/15/2013 01:58 AM, Jason Wang wrote:
>> Initializing them only when they're actually needed will do the trick here.
> I don't see so much memory allocation with qemu, the main problem I
> guess here is kvmtool does not support mergeable rx buffers ( does it?
> ). So guest must allocate 64K per packet which would be even worse in
> multiqueue case. If mergeable rx buffer was used, the receive buffer
> will only occupy about 256 * 4K (1M) which seems pretty acceptable here.
Yup, kvmtool doesn't do mergable RX at the moment.
I'll add support for that in, thanks for pointing it out!
Thanks,
Sasha
next prev parent reply other threads:[~2013-04-22 18:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 16:36 [PATCH 0/5] Usual batch of random ARM fixes for kvmtool Will Deacon
2013-04-11 16:36 ` [PATCH 1/5] kvm tools: arm: don't crash when no compatible CPU is found Will Deacon
2013-04-11 16:36 ` [PATCH 2/5] kvm tools: arm: add CPU compatible string to target structure Will Deacon
2013-04-11 16:36 ` [PATCH 3/5] kvm tools: arm: consolidate CPU node generation Will Deacon
2013-04-11 16:36 ` [PATCH 4/5] kvm tools: arm64: add support for AEM and Foundation models Will Deacon
2013-04-11 16:36 ` [PATCH 5/5] kvm tools: bump number of virtio MMIO vqueues Will Deacon
2013-04-11 16:45 ` [PATCH 0/5] Usual batch of random ARM fixes for kvmtool Sasha Levin
2013-04-12 6:52 ` Pekka Enberg
2013-04-12 8:30 ` Marc Zyngier
2013-04-12 8:50 ` Will Deacon
2013-04-11 20:02 ` virtio-net mq vq initialization (was: [PATCH 0/5] Usual batch of random ARM fixes for kvmtool) Sasha Levin
2013-04-12 11:36 ` Rusty Russell
2013-04-12 12:41 ` Will Deacon
2013-04-14 10:03 ` Michael S. Tsirkin
2013-04-13 21:23 ` virtio-net mq vq initialization Sasha Levin
2013-04-14 10:01 ` Michael S. Tsirkin
2013-04-14 15:16 ` Sasha Levin
2013-04-14 15:53 ` Michael S. Tsirkin
2013-04-14 15:59 ` Sasha Levin
2013-04-14 18:35 ` Michael S. Tsirkin
2013-04-15 2:55 ` Rusty Russell
2013-04-15 5:58 ` Jason Wang
2013-04-22 18:32 ` Sasha Levin [this message]
2013-04-12 7:12 ` [PATCH 0/5] Usual batch of random ARM fixes for kvmtool Pekka Enberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51758258.4010507@oracle.com \
--to=sasha.levin@oracle.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mst@redhat.com \
--cc=penberg@kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox