From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: KVM on NFS
Date: Wed, 17 Oct 2012 13:15:59 +0200
Message-ID: <507E936F.6070904@redhat.com>
References: <317CF30E-95D3-4836-9864-8B3C4F133F4B@syseleven.de> <507E8C90.2080708@redhat.com> <69228F0A-5CA0-4DF1-828A-027BC0E03B31@syseleven.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org
To: Andrew Holway <a.holway@syseleven.de>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:51759 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753526Ab2JQLQI (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 17 Oct 2012 07:16:08 -0400
In-Reply-To: <69228F0A-5CA0-4DF1-828A-027BC0E03B31@syseleven.de>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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