From: Paolo Bonzini <pbonzini@redhat.com>
To: Orit Wasserman <owasserm@redhat.com>
Cc: mst@redhat.com, chegu_vinod@hp.com, qemu-devel@nongnu.org,
quintela@redhat.com
Subject: Re: [Qemu-devel] [RFC 01/12] Add iov_writev to use writev to send iovec (also for files)
Date: Thu, 21 Mar 2013 10:23:01 +0100 [thread overview]
Message-ID: <514AD175.7090203@redhat.com> (raw)
In-Reply-To: <1363856971-4601-2-git-send-email-owasserm@redhat.com>
Il 21/03/2013 10:09, Orit Wasserman ha scritto:
> We use writev because sendmsg can only be used on socket fds.
>
> Signed-off-by: Orit Wasserman <owasserm@redhat.com>
> ---
> include/qemu/iov.h | 12 ++++++++++++
> util/iov.c | 36 ++++++++++++++++++++++++++++++++++++
> 2 files changed, 48 insertions(+)
>
> diff --git a/include/qemu/iov.h b/include/qemu/iov.h
> index 68d25f2..e26b7ba 100644
> --- a/include/qemu/iov.h
> +++ b/include/qemu/iov.h
> @@ -82,6 +82,18 @@ ssize_t iov_send_recv(int sockfd, struct iovec *iov, unsigned iov_cnt,
> #define iov_send(sockfd, iov, iov_cnt, offset, bytes) \
> iov_send_recv(sockfd, iov, iov_cnt, offset, bytes, true)
>
> +/*
> + * writes iovcnt buffers of data described by iov to the file associated with
> + * the file descriptor fd.
> + *
> + * @fd - file descriptor
> + * @iov - iov to write
> + * @invcnt - number of buffers to write
> + *
> + * @return - number of bytes return or -1 on error
> + */
> +ssize_t iov_writev(int fd, struct iovec *iov, unsigned iov_cnt);
> +
> /**
> * Produce a text hexdump of iovec `iov' with `iov_cnt' number of elements
> * in file `fp', prefixing each line with `prefix' and processing not more
> diff --git a/util/iov.c b/util/iov.c
> index 9dae318..bcd6e97 100644
> --- a/util/iov.c
> +++ b/util/iov.c
> @@ -197,6 +197,42 @@ ssize_t iov_send_recv(int sockfd, struct iovec *iov, unsigned iov_cnt,
> return ret;
> }
>
> +ssize_t iov_writev(int fd, struct iovec *iov, unsigned iov_cnt)
> +{
> +#if defined CONFIG_IOVEC && defined CONFIG_POSIX
> + ssize_t ret;
> +
> + do {
> + ret = writev(fd, iov, iov_cnt);
> + } while (ret < 0 && errno == EINTR);
> +
> + return ret;
> +#else
> + /* else send piece-by-piece */
> + /*XXX Note: windows has WSASend() and WSARecv() */
> + unsigned i = 0;
> + ssize_t ret = 0;
> + while (i < iov_cnt) {
> + ssize_t r = send(fd, iov[i].iov_base, iov[i].iov_len, 0);
> + if (r > 0) {
> + ret += r;
> + } else if (!r) {
> + break;
> + } else if (errno == EINTR) {
> + continue;
> + } else {
> + /* else it is some "other" error,
> + * only return if there was no data processed. */
> + if (ret == 0) {
> + ret = -1;
> + }
> + break;
> + }
> + i++;
> + }
> + return ret;
> +#endif
> +}
I think this code instead belongs in QEMUFile. qemu_fflush can use
either a single f->ops->writev_buffer call, or multiple
f->ops->put_buffer calls.
Paolo
> void iov_hexdump(const struct iovec *iov, const unsigned int iov_cnt,
> FILE *fp, const char *prefix, size_t limit)
>
next prev parent reply other threads:[~2013-03-21 9:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 9:09 [Qemu-devel] [RFC 00/12] Migration: Remove copying of guest ram pages Orit Wasserman
2013-03-21 9:09 ` [Qemu-devel] [RFC 01/12] Add iov_writev to use writev to send iovec (also for files) Orit Wasserman
2013-03-21 9:23 ` Paolo Bonzini [this message]
2013-03-21 9:09 ` [Qemu-devel] [RFC 02/12] Add QemuFileWritevBuffer QemuFileOps Orit Wasserman
2013-03-21 9:09 ` [Qemu-devel] [RFC 03/12] Add socket_writev_buffer function Orit Wasserman
2013-03-21 9:18 ` Paolo Bonzini
2013-03-21 9:47 ` Orit Wasserman
2013-03-21 9:47 ` Paolo Bonzini
2013-03-21 10:17 ` Orit Wasserman
2013-03-21 9:09 ` [Qemu-devel] [RFC 04/12] Add stdio_writev_buffer function Orit Wasserman
2013-03-21 9:28 ` Paolo Bonzini
2013-03-21 9:09 ` [Qemu-devel] [RFC 05/12] Add block_writev_buffer function Orit Wasserman
2013-03-21 9:09 ` [Qemu-devel] [RFC 06/12] Update bytes_xfer in qemu_put_byte Orit Wasserman
2013-03-21 9:09 ` [Qemu-devel] [RFC 07/12] Store the data to send also in iovec Orit Wasserman
2013-03-21 9:56 ` Paolo Bonzini
2013-03-21 11:10 ` Orit Wasserman
2013-03-21 11:14 ` Michael S. Tsirkin
2013-03-21 12:50 ` Orit Wasserman
2013-03-21 13:00 ` Paolo Bonzini
2013-03-21 9:09 ` [Qemu-devel] [RFC 08/12] Use writev ops instead of put_buffer ops Orit Wasserman
2013-03-21 9:09 ` [Qemu-devel] [RFC 09/12] More optimized qemu_put_be64/32/16 Orit Wasserman
2013-03-21 9:09 ` [Qemu-devel] [RFC 10/12] Add qemu_put_buffer_no_copy Orit Wasserman
2013-03-21 9:25 ` Paolo Bonzini
2013-03-23 16:27 ` Michael R. Hines
2013-03-25 8:11 ` Orit Wasserman
2013-03-25 13:05 ` Paolo Bonzini
2013-03-25 15:18 ` Michael R. Hines
2013-03-25 15:59 ` Paolo Bonzini
2013-03-21 9:09 ` [Qemu-devel] [RFC 11/12] Use qemu_put_buffer_no_copy for guest memory pages Orit Wasserman
2013-03-21 9:09 ` [Qemu-devel] [RFC 12/12] Bye Bye put_buffer Orit Wasserman
2013-03-21 9:29 ` [Qemu-devel] [RFC 00/12] Migration: Remove copying of guest ram pages Paolo Bonzini
2013-03-21 10:05 ` Orit Wasserman
2013-03-21 9:48 ` Michael S. Tsirkin
2013-03-21 9:53 ` Paolo Bonzini
2013-03-21 11:09 ` Michael S. Tsirkin
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=514AD175.7090203@redhat.com \
--to=pbonzini@redhat.com \
--cc=chegu_vinod@hp.com \
--cc=mst@redhat.com \
--cc=owasserm@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).