From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Krdod-0008K9-39 for qemu-devel@nongnu.org; Sun, 19 Oct 2008 15:19:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Krdob-0008Hp-CY for qemu-devel@nongnu.org; Sun, 19 Oct 2008 15:19:50 -0400 Received: from [199.232.76.173] (port=39145 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Krdob-0008Hh-9b for qemu-devel@nongnu.org; Sun, 19 Oct 2008 15:19:49 -0400 Received: from bsdimp.com ([199.45.160.85]:52432 helo=harmony.bsdimp.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Krdoa-0006w5-Pm for qemu-devel@nongnu.org; Sun, 19 Oct 2008 15:19:49 -0400 Date: Sun, 19 Oct 2008 13:17:07 -0600 (MDT) Message-Id: <20081019.131707.1678758304.imp@bsdimp.com> Subject: Re: [Qemu-devel] [RFC] Disk integrity in QEMU From: "M. Warner Losh" In-Reply-To: <48FB7B26.2090903@redhat.com> References: <48FAF751.8010806@redhat.com> <20081019181026.GU19428@kernel.dk> <48FB7B26.2090903@redhat.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, avi@redhat.com Cc: chrisw@redhat.com, markmc@redhat.com, kvm-devel@lists.sourceforge.net, Laurent.Vivier@bull.net, ryanh@us.ibm.com In message: <48FB7B26.2090903@redhat.com> Avi Kivity writes: : >> Sounds like a bug. Shouldn't Linux disable the write cache unless the : >> user explicitly enables it, if NCQ is available? NCQ should provide : >> acceptable throughput even without the write cache. : >> : > : > How can it be a bug? : : If it puts my data at risk, it's a bug. I can understand it for IDE, : but not for SATA with NCQ. So wouldn't async mounts by default be a bug too? Warner