All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: kvm-ppc-devel@lists.sourceforge.net,
	Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>,
	Rusty Russell <rusty@ozlabs.au.ibm.com>,
	kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: [kvm-ppc-devel] booting from virtio-blk
Date: Tue, 01 Apr 2008 17:05:40 +0000	[thread overview]
Message-ID: <47F26B64.5090101@us.ibm.com> (raw)
In-Reply-To: <1207066432.6214.29.camel@basalt>

Hollis Blanchard wrote:
> On Tue, 2008-04-01 at 09:46 -0500, Anthony Liguori wrote:
>   
> Thanks Anthony, you've saved me a lot of debug time! Rusty, doing 64-bit
> PCI config space accesses with ioread8() definitely violates the
> principle of least surprises, and would have taken me a long time to
> track down. :(
>
> Attached is a boot log of a PowerPC guest booting from virtio-blk root.
>
> "ramdisk_image" is the standard ~4MB image provided with DENX Embedded
> Linux Development Kit. Booting is also *way* faster than NFS root (a few
> seconds to get to a shell :) .
>   

That suggests you have vmexit latency issues.  A 4MB disk is pretty much 
entirely cachable in memory so you probably end up with only a handful 
of requests to get the full disk into memory.  Conversely, when using 
NFS, every single filesystem operation requests in multiple packets 
being delivered/received.  To complicate matters further, NFS means you 
won't be doing any dentry caching so every single filesystem access will 
result in requests as opposed to just the first access.

What sort of ping latency do you get with virtio-net?

Regards,

Anthony Liguori

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel

WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <aliguori@us.ibm.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: kvm-ppc-devel@lists.sourceforge.net,
	Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>,
	Rusty Russell <rusty@ozlabs.au.ibm.com>,
	kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: booting from virtio-blk
Date: Tue, 01 Apr 2008 12:05:40 -0500	[thread overview]
Message-ID: <47F26B64.5090101@us.ibm.com> (raw)
In-Reply-To: <1207066432.6214.29.camel@basalt>

Hollis Blanchard wrote:
> On Tue, 2008-04-01 at 09:46 -0500, Anthony Liguori wrote:
>   
> Thanks Anthony, you've saved me a lot of debug time! Rusty, doing 64-bit
> PCI config space accesses with ioread8() definitely violates the
> principle of least surprises, and would have taken me a long time to
> track down. :(
>
> Attached is a boot log of a PowerPC guest booting from virtio-blk root.
>
> "ramdisk_image" is the standard ~4MB image provided with DENX Embedded
> Linux Development Kit. Booting is also *way* faster than NFS root (a few
> seconds to get to a shell :) .
>   

That suggests you have vmexit latency issues.  A 4MB disk is pretty much 
entirely cachable in memory so you probably end up with only a handful 
of requests to get the full disk into memory.  Conversely, when using 
NFS, every single filesystem operation requests in multiple packets 
being delivered/received.  To complicate matters further, NFS means you 
won't be doing any dentry caching so every single filesystem access will 
result in requests as opposed to just the first access.

What sort of ping latency do you get with virtio-net?

Regards,

Anthony Liguori

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

  reply	other threads:[~2008-04-01 17:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 12:01 [kvm-ppc-devel] [PATCH] kvm(ppc)-userspace: initialize virtio-block ehrhardt
2008-04-01 12:08 ` [kvm-ppc-devel] [PATCH] kvm(ppc)-userspace: initialize Christian Ehrhardt
2008-04-01 14:33   ` [kvm-ppc-devel] [PATCH] kvm(ppc)-userspace: Hollis Blanchard
2008-04-01 14:46   ` [kvm-ppc-devel] [PATCH] kvm(ppc)-userspace: initialize Anthony Liguori
2008-04-01 16:13     ` [kvm-ppc-devel] booting from virtio-blk Hollis Blanchard
2008-04-01 16:13       ` Hollis Blanchard
2008-04-01 17:05       ` Anthony Liguori [this message]
2008-04-01 17:05         ` Anthony Liguori
2008-04-01 17:09       ` [kvm-ppc-devel] " Anthony Liguori
2008-04-01 17:09         ` Anthony Liguori
2008-04-01 20:36         ` [kvm-ppc-devel] " Benjamin Herrenschmidt
2008-04-01 20:36           ` Benjamin Herrenschmidt
2008-04-01 21:03           ` Anthony Liguori
2008-04-01 21:03             ` Anthony Liguori
2008-04-01 21:14             ` Benjamin Herrenschmidt
2008-04-01 21:14               ` Benjamin Herrenschmidt
2008-04-01 21:18             ` Hollis Blanchard
2008-04-01 21:18               ` Hollis Blanchard
2008-04-01 21:24               ` Benjamin Herrenschmidt
2008-04-01 21:24                 ` Benjamin Herrenschmidt
2008-04-02 14:52   ` [kvm-ppc-devel] [PATCH] kvm(ppc)-userspace: initialize Anthony Liguori

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=47F26B64.5090101@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=ehrhardt@linux.vnet.ibm.com \
    --cc=hollisb@us.ibm.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=kvm-ppc-devel@lists.sourceforge.net \
    --cc=rusty@ozlabs.au.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.