public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: Sasha Levin <sasha.levin@oracle.com>,
	Will Deacon <Will.Deacon@arm.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 0/5] Usual batch of random ARM fixes for kvmtool
Date: Fri, 12 Apr 2013 09:30:18 +0100	[thread overview]
Message-ID: <5167C61A.7030400@arm.com> (raw)
In-Reply-To: <5167AF3C.8060409@kernel.org>

Hi Pekka,

On 12/04/13 07:52, Pekka Enberg wrote:
> On 04/11/2013 12:36 PM, Will Deacon wrote:
>>> Without multi-queue, we can boot Debian Wheezy to a prompt in 38MB. With
>>> the new changes, that increases to 170MB! Any chance we can try and tackle
>>> this regression please? I keep getting bitten by the OOM killer :(
> 
> On 04/11/2013 07:45 PM, Sasha Levin wrote:
>> That's definitely unwanted.
>>
>> I'll look into it and try sending something out today/tomorrow.
> 
> That's very unfortunate. Can you please confirm that reverting commit 
> e026314820acc3cc967308355f3746aca238fda4 ("kvm tools: virtio-net 
> multiqueue support") fixes it? If fixing the issue turns out to be 
> difficult, we should just take multi-queue out until the issues is resolved.

It does, at least for an MMIO based setup.

It would be a pity to completely loose the functionality though. Surely
we can find a way to initialize the extra queues on demand. And if not,
maybe introduce some kind of tunable parameter...

Cheers,

	M.
-- 
Jazz is not dead. It just smells funny...


  reply	other threads:[~2013-04-12  8:30 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 [this message]
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
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=5167C61A.7030400@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=Will.Deacon@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=penberg@kernel.org \
    --cc=sasha.levin@oracle.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