All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>,
	khoa@us.ibm.com, Paolo Bonzini <pbonzini@redhat.com>,
	asias@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 07/11] iov: add iov_discard() to remove data
Date: Thu, 6 Dec 2012 13:36:42 +0200	[thread overview]
Message-ID: <20121206113642.GM10837@redhat.com> (raw)
In-Reply-To: <1354740430-22452-8-git-send-email-stefanha@redhat.com>

On Wed, Dec 05, 2012 at 09:47:06PM +0100, Stefan Hajnoczi wrote:
> The iov_discard() function removes data from the front or back of the
> vector.  This is useful when peeling off header/footer structs.
> 
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
>  iov.c | 41 +++++++++++++++++++++++++++++++++++++++++
>  iov.h | 13 +++++++++++++
>  2 files changed, 54 insertions(+)
> 
> diff --git a/iov.c b/iov.c
> index a81eedc..6eed089 100644
> --- a/iov.c
> +++ b/iov.c
> @@ -354,3 +354,44 @@ size_t qemu_iovec_memset(QEMUIOVector *qiov, size_t offset,
>  {
>      return iov_memset(qiov->iov, qiov->niov, offset, fillc, bytes);
>  }
> +
> +size_t iov_discard(struct iovec **iov, unsigned int *iov_cnt, ssize_t bytes)
> +{
> +    size_t total = 0;
> +    struct iovec *cur;
> +    int direction;
> +
> +    if (*iov_cnt == 0) {
> +        return 0;
> +    }
> +
> +    if (bytes < 0) {
> +        bytes = -bytes;
> +        direction = -1;
> +        cur = *iov + (*iov_cnt - 1);
> +    } else {
> +        direction = 1;
> +        cur = *iov;
> +    }
> +
> +    while (*iov_cnt > 0) {
> +        if (cur->iov_len > bytes) {
> +            if (direction > 0) {
> +                cur->iov_base += bytes;
> +            }
> +            cur->iov_len -= bytes;
> +            total += bytes;
> +            break;
> +        }
> +
> +        bytes -= cur->iov_len;
> +        total += cur->iov_len;
> +        cur += direction;
> +        *iov_cnt -= 1;
> +    }
> +
> +    if (direction > 0) {
> +        *iov = cur;
> +    }
> +    return total;
> +}
> diff --git a/iov.h b/iov.h
> index 34c8ec9..d6d1fa6 100644
> --- a/iov.h
> +++ b/iov.h
> @@ -95,3 +95,16 @@ void iov_hexdump(const struct iovec *iov, const unsigned int iov_cnt,
>  unsigned iov_copy(struct iovec *dst_iov, unsigned int dst_iov_cnt,
>                   const struct iovec *iov, unsigned int iov_cnt,
>                   size_t offset, size_t bytes);
> +
> +/*
> + * Remove a given number of bytes from the front or back of a vector.
> + * This may update iov and/or iov_cnt to exclude iovec elements that are
> + * no longer required.
> + *
> + * Data is discarded from the front of the vector if bytes is positive and
> + * from the back of the vector if bytes is negative.

I think I already commented on this: I think this interface is too tricky,
and use of ssize_t is a bad idea since most of code uses size_t:
you might start getting integer overflow errors if you convert.

Better to have
size_t iov_discard_front(struct iovec **iov, unsigned int *iov_cnt, ssize_t bytes);
size_t iov_discard_back(struct iovec **iov, unsigned int *iov_cnt, ssize_t bytes);

which explicitly do the right thing.

The fix up users to use size_t everywhere.

> + *
> + * The number of bytes actually discarded is returned.  This number may be
> + * smaller than requested if the vector is too small.
> + */
> +size_t iov_discard(struct iovec **iov, unsigned int *iov_cnt, ssize_t bytes);
> -- 
> 1.8.0.1

  reply	other threads:[~2012-12-06 11:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05 20:46 [Qemu-devel] [PATCH v5 00/11] virtio: virtio-blk data plane Stefan Hajnoczi
2012-12-05 20:47 ` [Qemu-devel] [PATCH v5 01/11] raw-posix: add raw_get_aio_fd() for virtio-blk-data-plane Stefan Hajnoczi
2012-12-05 20:47 ` [Qemu-devel] [PATCH v5 02/11] configure: add CONFIG_VIRTIO_BLK_DATA_PLANE Stefan Hajnoczi
2012-12-05 20:47 ` [Qemu-devel] [PATCH v5 03/11] dataplane: add host memory mapping code Stefan Hajnoczi
2012-12-09  4:02   ` liu ping fan
2012-12-09 10:36     ` Stefan Hajnoczi
2012-12-05 20:47 ` [Qemu-devel] [PATCH v5 04/11] dataplane: add virtqueue vring code Stefan Hajnoczi
2012-12-06 11:22   ` Michael S. Tsirkin
2012-12-06 12:53     ` Stefan Hajnoczi
2012-12-07 14:07   ` Kevin Wolf
2012-12-07 14:46     ` Stefan Hajnoczi
2012-12-05 20:47 ` [Qemu-devel] [PATCH v5 05/11] dataplane: add event loop Stefan Hajnoczi
2012-12-05 20:47 ` [Qemu-devel] [PATCH v5 06/11] dataplane: add Linux AIO request queue Stefan Hajnoczi
2012-12-07 14:21   ` Kevin Wolf
2012-12-10 13:05     ` Stefan Hajnoczi
2012-12-05 20:47 ` [Qemu-devel] [PATCH v5 07/11] iov: add iov_discard() to remove data Stefan Hajnoczi
2012-12-06 11:36   ` Michael S. Tsirkin [this message]
2012-12-06 14:07     ` Stefan Hajnoczi
2012-12-05 20:47 ` [Qemu-devel] [PATCH v5 08/11] test-iov: add iov_discard() testcase Stefan Hajnoczi
2012-12-05 20:47 ` [Qemu-devel] [PATCH v5 09/11] iov: add qemu_iovec_concat_iov() Stefan Hajnoczi
2012-12-05 20:47 ` [Qemu-devel] [PATCH v5 10/11] dataplane: add virtio-blk data plane code Stefan Hajnoczi
2012-12-06  7:35   ` Paolo Bonzini
2012-12-06 14:03     ` Stefan Hajnoczi
2012-12-07  6:06     ` Stefan Hajnoczi
2012-12-07 10:51       ` Paolo Bonzini
2012-12-06 11:33   ` Michael S. Tsirkin
2012-12-07  5:43     ` Stefan Hajnoczi
2012-12-07 18:04   ` Kevin Wolf
2012-12-10 13:06     ` Stefan Hajnoczi
2012-12-05 20:47 ` [Qemu-devel] [PATCH v5 11/11] virtio-blk: add x-data-plane=on|off performance feature Stefan Hajnoczi
2012-12-06 11:38 ` [Qemu-devel] [PATCH v5 00/11] virtio: virtio-blk data plane Michael S. Tsirkin
2012-12-07  6:12   ` Stefan Hajnoczi
2012-12-07  2:43 ` Liu Yuan
2012-12-07  5:46   ` Stefan Hajnoczi

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=20121206113642.GM10837@redhat.com \
    --to=mst@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=asias@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=khoa@us.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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 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.