All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: Xiao Guangrong <guangrong.xiao@linux.intel.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel@nongnu.org, "Zhang,
	Haozhong" <haozhong.zhang@intel.com>
Subject: Re: [Qemu-devel] Question about vNVDIMM file format
Date: Wed, 18 May 2016 11:50:12 +0100	[thread overview]
Message-ID: <20160518105011.GF1683@redhat.com> (raw)
In-Reply-To: <573C1414.1050608@linux.intel.com>

On Wed, May 18, 2016 at 03:04:52PM +0800, Xiao Guangrong wrote:
> On 05/17/2016 02:25 AM, Richard W.M. Jones wrote:
> >(a) How necessary is the ACPI dependency?  We disable ACPI because it
> >is quite slow, adding something like 150-200ms to the boot process
> >(every millisecond counts for us!).  Because I previously never needed
> >ACPI, I never really looked into why this is, and it could be
> >something quite simple, so I'm going to look at this issue next.  I
> >understand that NVDIMMs are not regular (eg) PCI devices, so ordinary
> >device probing isn't going to work, and that probably answers the
> >question why you need to use ACPI.
> 
> Yes, ACPI is necessary to export NVDIMM devices. The good news is that
> Intel is working on ‘lite QEMU’ which only has basic/simplest ACPI
> support. Haozhong, who has been CCed, is working on it.

I remeasured the ACPI overhead with the latest upstream kernel & qemu,
it has dropped to under 20ms, so now I've just unconditionally enabled
ACPI.

> >(c) I've got the root filesystem (which is actually ext2, but using
> >the ext4.ko driver) mounted with -o dax.  What benefits / differences
> >should I observe?  Just general reduced memory / page cache usage?
> >
> 
> And better performance as slow IO path is not needed anymore. :)
> 
> However, there is potential issue if it is not backend by real NVDIMM
> hardware, the data is not persistent. We are going to resolve it by
> emulating PCOMMIT and do msync properly.

I'm using share=off (ie. MMAP_PRIVATE), because for this appliance
model I don't want writes to go to the backing disk.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org

  parent reply	other threads:[~2016-05-18 10:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16 15:04 [Qemu-devel] Question about vNVDIMM file format Richard W.M. Jones
2016-05-16 16:53 ` Stefan Hajnoczi
2016-05-16 18:25   ` Richard W.M. Jones
2016-05-18  7:04     ` Xiao Guangrong
2016-05-18  8:11       ` Zhang, Haozhong
2016-05-18 10:50       ` Richard W.M. Jones [this message]
2016-05-18 17:36       ` Richard W.M. Jones
2016-05-16 17:39 ` Xiao Guangrong

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=20160518105011.GF1683@redhat.com \
    --to=rjones@redhat.com \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=haozhong.zhang@intel.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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.