All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: "Xen-Devel (xen-devel@lists.xensource.com)"
	<xen-devel@lists.xensource.com>
Subject: Re: Writing to a ramdisk in a PV domain is SLLLOOOWWW?!?
Date: Thu, 06 May 2010 10:42:53 -0700	[thread overview]
Message-ID: <4BE2FF9D.9010500@goop.org> (raw)
In-Reply-To: <89f1cead-b77d-4294-ab12-5e05344ed346@default>

On 05/05/2010 11:14 AM, Dan Magenheimer wrote:
> Has anyone tried using a ramdisk in a PV domain?
>
> I'm trying it in an experiment to compare swapping to
> a ramdisk against tmem (frontswap) performance
> (suggested as a performance test on lkml).
>
> Writing to the ramdisk appears to be VERY VERY slow,
> elapsed time in the guest is several times larger than
> user+sys, and xentop shows the guest consuming vcpu
> seconds at about the user+sys rate.  Note that
> this is when tmem is turned off and there is no
> vhd swap disk configured.
>
> I'm suspecting that writing to ramdisk must be causing
> some interesting/expensive PV pagetable behavior?
> Or maybe somehow /dev/ram0 is getting routed through
> qemu?  Or ??
>   

I haven't looked at ramdisk, but I'm pretty sure there's nothing special
about accessing it.  The only thing I can think of is that if you're
using a 32bit highmem system then you may be being hit by lots of kmap
overhead.  But on a 64-bit system, AFAIK, it should just be memory copies.

    J

  parent reply	other threads:[~2010-05-06 17:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 18:14 Writing to a ramdisk in a PV domain is SLLLOOOWWW?!? Dan Magenheimer
2010-05-05 20:16 ` Dan Magenheimer
2010-05-06 17:42 ` Jeremy Fitzhardinge [this message]
2010-05-06 21:02   ` Dan Magenheimer
2010-05-06 22:04     ` Santos, Jose Renato G
2010-05-06 22:26       ` Jeremy Fitzhardinge

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=4BE2FF9D.9010500@goop.org \
    --to=jeremy@goop.org \
    --cc=dan.magenheimer@oracle.com \
    --cc=xen-devel@lists.xensource.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.