All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Andrew Holway <a.holway@syseleven.de>
Cc: kvm@vger.kernel.org
Subject: Re: KVM on NFS
Date: Wed, 17 Oct 2012 12:46:40 +0200	[thread overview]
Message-ID: <507E8C90.2080708@redhat.com> (raw)
In-Reply-To: <317CF30E-95D3-4836-9864-8B3C4F133F4B@syseleven.de>

On 10/17/2012 11:20 AM, Andrew Holway wrote:
> Hello,
> 
> I am testing KVM on an Oracle NFS box that I have.
> 
> Does the list have any advice on best practice? I remember reading that there is stuff you can do with I/O schedulers and stuff to make it more efficient.
> 
> My VMs will primarily be running mysql databases. I am currently using o_direct.
> 

O_DIRECT is good.  I/O schedulers don't affect NFS so no need to tune
anything on the host.  You might experiment with switching to the
deadline scheduler in the guest.


-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2012-10-17 10:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17  9:20 KVM on NFS Andrew Holway
2012-10-17 10:46 ` Avi Kivity [this message]
2012-10-17 11:04   ` Andrew Holway
2012-10-17 11:15     ` Avi Kivity
2012-10-19 14:17   ` Banyan He

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=507E8C90.2080708@redhat.com \
    --to=avi@redhat.com \
    --cc=a.holway@syseleven.de \
    --cc=kvm@vger.kernel.org \
    /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.