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 13:15:59 +0200 [thread overview]
Message-ID: <507E936F.6070904@redhat.com> (raw)
In-Reply-To: <69228F0A-5CA0-4DF1-828A-027BC0E03B31@syseleven.de>
On 10/17/2012 01:04 PM, Andrew Holway wrote:
>
>
>> 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.
>
> Ill give it a go. Any ideas how I should be tuning my NFS?
Not really. The defaults should work well enough.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-10-17 11:16 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
2012-10-17 11:04 ` Andrew Holway
2012-10-17 11:15 ` Avi Kivity [this message]
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=507E936F.6070904@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).