[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v3 9/9] coalesce adjacent iovecs
From: |
Michael S. Tsirkin |
Subject: |
Re: [Qemu-devel] [PATCH v3 9/9] coalesce adjacent iovecs |
Date: |
Thu, 21 Mar 2013 20:33:10 +0200 |
On Thu, Mar 21, 2013 at 07:22:01PM +0100, Juan Quintela wrote:
> "Michael S. Tsirkin" <address@hidden> 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
- Re: [Qemu-devel] [PATCH v3 7/9] Add qemu_put_buffer_no_copy, (continued)
Re: [Qemu-devel] [PATCH v3 9/9] coalesce adjacent iovecs, Juan Quintela, 2013/03/21
[Qemu-devel] [PATCH v3 8/9] Use qemu_put_buffer_no_copy for guest memory pages, Orit Wasserman, 2013/03/21
Re: [Qemu-devel] [PATCH v3 0/9] Migration: Remove copying of guest ram pages, Paolo Bonzini, 2013/03/21
Re: [Qemu-devel] [PATCH v3 0/9] Migration: Remove copying of guest ram pages, Juan Quintela, 2013/03/21