From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=53587 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OghcX-0004DQ-2s for qemu-devel@nongnu.org; Wed, 04 Aug 2010 13:19:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OghcV-0001gt-Kv for qemu-devel@nongnu.org; Wed, 04 Aug 2010 13:19:12 -0400 Received: from mx1.redhat.com ([209.132.183.28]:17940) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OghcV-0001ge-EN for qemu-devel@nongnu.org; Wed, 04 Aug 2010 13:19:11 -0400 Message-ID: <4C59A108.3090807@redhat.com> Date: Wed, 04 Aug 2010 20:19:04 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Anyone seeing huge slowdown launching qemu with Linux 2.6.35? References: <4C5847CD.9080107@codemonkey.ws> <4C5848C7.3090806@redhat.com> <4C584982.5000108@codemonkey.ws> <4C584B66.5070404@redhat.com> <4C5854F1.3000905@codemonkey.ws> <4C5858B2.9090801@redhat.com> <4C585F5B.5070502@codemonkey.ws> <4C58635B.7020407@redhat.com> <20100803191346.GA28523@amd.home.annexia.org> <4C586C6E.9030002@redhat.com> <20100803200057.GB28523@amd.home.annexia.org> <4C5880BC.2080802@codemonkey.ws> <4C588685.8070509@redhat.com> <4C588B7D.5040902@codemonkey.ws> <4C591D87.5020809@redhat.com> <4C5962DA.4090108@codemonkey.ws> <4C5998EB.2050804@redhat.com> <4C59996A.9010402@codemonkey.ws> <58DD5B14-F1A9-408C-982A-A29E0A7FACF2@suse.de> <4C599A27.9000602@codemonkey.ws> <4C599CE1.30501@redhat.com> In-Reply-To: <4C599CE1.30501@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Gleb Natapov , kvm@vger.kernel.org, "Richard W.M. Jones" , qemu-devel@nongnu.org, Alexander Graf On 08/04/2010 08:01 PM, Paolo Bonzini wrote: > > That's another story and I totally agree here, but not reusing > /dev/sd* is not intrinsic in the design of virtio-blk (and one thing > that Windows gets right; everything is SCSI, period). > I don't really get why everything must be SCSI. Everything must support read, write, a few other commands, and a large set of optional commands. But why map them all to SCSI? What's the magic? -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.