From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=33918 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ou1aa-0003cv-3y for qemu-devel@nongnu.org; Fri, 10 Sep 2010 07:16:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Ou1aY-0000WI-Tb for qemu-devel@nongnu.org; Fri, 10 Sep 2010 07:16:16 -0400 Received: from mx1.redhat.com ([209.132.183.28]:64022) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Ou1aY-0000WD-Mq for qemu-devel@nongnu.org; Fri, 10 Sep 2010 07:16:14 -0400 Message-ID: <4C8A136F.5080806@redhat.com> Date: Fri, 10 Sep 2010 14:15:59 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [RFC] qed: Add QEMU Enhanced Disk format References: <4C874812.9090807@redhat.com> <395D4377-00F9-4765-94C4-470BDFA1F96E@suse.de> <4C874F22.6060802@redhat.com> <20100908153857.GA30438@lst.de> <4C87BA12.5040909@codemonkey.ws> <20100908202336.GA7855@lst.de> <4C87F202.5000602@codemonkey.ws> <20100909023550.GA19336@lst.de> <4C887D9A.3020702@redhat.com> <20100909210137.GA30588@lst.de> In-Reply-To: <20100909210137.GA30588@lst.de> 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: Christoph Hellwig Cc: Kevin Wolf , Stefan Hajnoczi , Stefan Hajnoczi , Alexander Graf , qemu-devel@nongnu.org On 09/10/2010 12:01 AM, Christoph Hellwig wrote: > On Thu, Sep 09, 2010 at 09:24:26AM +0300, Avi Kivity wrote: >> The other thing we can do is defragment the logical image, then >> defragment the underlying file (if the filesystem supports it, issue the >> appropriate ioctl, otherwise defragment to a new file which you write >> linearly). > What's what the defragmentation code does in a slightly optimized > fashion anyway - so if you want to do it from qemu just do it that > way. Don't even bother calling the filesystem ioctls directly given > that they just implementa low-level helpers and the actual logic is > in the userspace side of the defragmentation tools. Well, if we ask the kernel do to it, we gain any future optimizations as well. For example, if parts of the file are already defragmented, the kernel can avoid moving that data. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.