From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:38375)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1UIkI0-0003YL-R5
	for qemu-devel@nongnu.org; Thu, 21 Mar 2013 14:32:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1UIkHx-0002vP-Ms
	for qemu-devel@nongnu.org; Thu, 21 Mar 2013 14:32:36 -0400
Received: from mx1.redhat.com ([209.132.183.28]:27310)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1UIkHx-0002v8-Ej
	for qemu-devel@nongnu.org; Thu, 21 Mar 2013 14:32:33 -0400
Date: Thu, 21 Mar 2013 20:33:10 +0200
From: "Michael S. Tsirkin" <mst@redhat.com>
Message-ID: <20130321183310.GB4800@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>
	<20130321174635.GA4112@redhat.com> <8738vopq9i.fsf@elfo.elfo>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8738vopq9i.fsf@elfo.elfo>
Subject: Re: [Qemu-devel] [PATCH v3 9/9] coalesce adjacent iovecs
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Juan Quintela <quintela@redhat.com>
Cc: Orit Wasserman <owasserm@redhat.com>, chegu_vinod@hp.com, qemu-devel@nongnu.org, pbonzini@redhat.com

On Thu, Mar 21, 2013 at 07:22:01PM +0100, Juan Quintela wrote:
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
> 
> >> <header>
> >> <page>
> >> <header>
> >> <page>
> >> <header>
> >> <page>
> >> 
> >> 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.
> 
> RDMA requires de pages lock into memory, no?
> 
> Later, Juan.

That's a separate issue, but the point is it is asynchronous.
It can be made to behave exactly the same implementing this API:

	- send async: lock, send
	- flush: poll for completion, unlock