From: Juan Quintela <quintela@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: owasserm@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 6/6] qemu-file: do not use stdio for qemu_fdopen
Date: Tue, 09 Apr 2013 15:30:28 +0200 [thread overview]
Message-ID: <87y5crbzm3.fsf@elfo.elfo> (raw)
In-Reply-To: <1364402192-18169-7-git-send-email-pbonzini@redhat.com> (Paolo Bonzini's message of "Wed, 27 Mar 2013 17:36:32 +0100")
Paolo Bonzini <pbonzini@redhat.com> wrote:
> This uses system calls directly for Unix file descriptors, so that the
> efficient writev_buffer can be used. Pay attention to the possibility
> of partial writes in writev.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
> +static ssize_t unix_writev_buffer(void *opaque, struct iovec *iov, int iovcnt)
> +{
> + QEMUFileSocket *s = opaque;
> + ssize_t len, offset;
> + ssize_t size = iov_size(iov, iovcnt);
> + ssize_t total = 0;
> +
> + assert(iovcnt > 0);
> + offset = 0;
> + while (size > 0) {
> + /* Find the next start position; skip all full-sized vector elements */
> + while (offset >= iov[0].iov_len) {
> + offset -= iov[0].iov_len;
> + iov++, iovcnt--;
> + }
> +
> + /* skip `offset' bytes from the (now) first element, undo it on exit */
> + assert(iovcnt > 0);
> + iov[0].iov_base += offset;
> + iov[0].iov_len -= offset;
> +
> + do {
> + len = writev(s->fd, iov, iovcnt);
> + } while (len == -1 && errno == EINTR);
> + if (len == -1) {
> + return -errno;
> + }
> +
> + /* Undo the changes above */
> + iov[0].iov_base -= offset;
> + iov[0].iov_len += offset;
> +
> + /* Prepare for the next iteration */
> + offset += len;
> + total += len;
> + size -= len;
> + }
> +
> + return total;
> +}
This code is very similar to the one in the iov_send_recv(), but I
can't think on a trivial way to share it :p
Later, Juan.
next prev parent reply other threads:[~2013-04-09 13:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 16:36 [Qemu-devel] [PATCH 0/6] migration: followups for writev patches Paolo Bonzini
2013-03-27 16:36 ` [Qemu-devel] [PATCH 1/6] qemu-file: drop socket_put_buffer Paolo Bonzini
2013-04-09 13:20 ` Juan Quintela
2013-03-27 16:36 ` [Qemu-devel] [PATCH 2/6] iov: reorganize iov_send_recv, part 1 Paolo Bonzini
2013-04-09 13:18 ` Juan Quintela
2013-03-27 16:36 ` [Qemu-devel] [PATCH 3/6] iov: reorganize iov_send_recv, part 2 Paolo Bonzini
2013-04-09 13:23 ` Juan Quintela
2013-03-27 16:36 ` [Qemu-devel] [PATCH 4/6] iov: reorganize iov_send_recv, part 3 Paolo Bonzini
2013-04-09 13:24 ` Juan Quintela
2013-03-27 16:36 ` [Qemu-devel] [PATCH 5/6] iov: handle partial writes from sendmsg and recvmsg Paolo Bonzini
2013-04-09 13:27 ` Juan Quintela
2013-03-27 16:36 ` [Qemu-devel] [PATCH 6/6] qemu-file: do not use stdio for qemu_fdopen Paolo Bonzini
2013-04-09 13:30 ` Juan Quintela [this message]
2013-04-16 21:09 ` Anthony Liguori
2013-04-03 8:08 ` [Qemu-devel] [PATCH 0/6] migration: followups for writev patches Orit Wasserman
2013-04-16 15:41 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2013-04-17 9:46 [Qemu-devel] [PULL (rebased) " Paolo Bonzini
2013-04-17 9:46 ` [Qemu-devel] [PATCH 6/6] qemu-file: do not use stdio for qemu_fdopen Paolo Bonzini
2013-04-20 18:53 ` Blue Swirl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y5crbzm3.fsf@elfo.elfo \
--to=quintela@redhat.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.