From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:47592) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UIjYy-0000vH-Oy for qemu-devel@nongnu.org; Thu, 21 Mar 2013 13:46:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UIjYv-0003ff-UR for qemu-devel@nongnu.org; Thu, 21 Mar 2013 13:46:04 -0400 Received: from mx1.redhat.com ([209.132.183.28]:23169) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UIjYv-0003fa-Mi for qemu-devel@nongnu.org; Thu, 21 Mar 2013 13:46:01 -0400 Date: Thu, 21 Mar 2013 19:46:35 +0200 From: "Michael S. Tsirkin" Message-ID: <20130321174635.GA4112@redhat.com> References: <1363881940-27505-1-git-send-email-owasserm@redhat.com> <1363881940-27505-10-git-send-email-owasserm@redhat.com> <20130321161608.GE1925@redhat.com> <514B34FE.6010901@redhat.com> <20130321162912.GH1925@redhat.com> <877gl0ps0h.fsf@elfo.elfo> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <877gl0ps0h.fsf@elfo.elfo> Subject: Re: [Qemu-devel] [PATCH v3 9/9] coalesce adjacent iovecs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Juan Quintela Cc: Orit Wasserman , chegu_vinod@hp.com, qemu-devel@nongnu.org, pbonzini@redhat.com On Thu, Mar 21, 2013 at 06:44:14PM +0100, Juan Quintela wrote: > "Michael S. Tsirkin" wrote: > > On Thu, Mar 21, 2013 at 06:27:42PM +0200, Orit Wasserman wrote: > >> On 03/21/2013 06:16 PM, Michael S. Tsirkin wrote: > >> > On Thu, Mar 21, 2013 at 06:05:40PM +0200, Orit Wasserman wrote: > >> >> This way we send one big buffer instead of many small ones > >> >> > >> >> Signed-off-by: Orit Wasserman > >> > > >> > Why does this happen BTW? > >> > >> It happens in the last phase when we send the device state that > >> consists of a lot > >> bytes and int field that are written using qemu_put_byte/be16/... > >> > > > > Confused I thought device_state does not use _nocopy? > > My idea of using vmsplice relies exactly on this: > > we can not splice device state ... > > > As it is today, I am not sure that we can use vmsplice() because we > are sending: > > >
> >
> >
> > > We can optimize at some pount to write a bigger/different header and > sent a bunch of pages together, but just now we don't have that code. > > Later, Juan. Sending the page can do vmsplice, can't it? Multipage is likely a good idea anyway, e.g. RDMA wants to do this too.