qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 08/12] file-posix: Move read/write operation logic out of aio_worker()
Date: Thu, 15 Nov 2018 17:17:56 +0100	[thread overview]
Message-ID: <20181115161756.GE12677@localhost.localdomain> (raw)
In-Reply-To: <20181031215622.27690-9-kwolf@redhat.com>

Am 31.10.2018 um 22:56 hat Kevin Wolf geschrieben:
> aio_worker() for reads and writes isn't boring enough yet. It still does
> some postprocessing for handling short reads and turning the result into
> the right return value.
> 
> However, there is no reason why handle_aiocb_rw() couldn't do the same,
> and even without duplicating code between the read and write path. So
> move the code there.
> 
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>

> @@ -1354,7 +1356,21 @@ static ssize_t handle_aiocb_rw(RawPosixAIOData *aiocb)
>      }
>      qemu_vfree(buf);
>  
> -    return nbytes;
> +out:
> +    if (nbytes == aiocb->aio_nbytes) {
> +        return 0;
> +    } else if (nbytes >= 0 && nbytes < aiocb->aio_nbytes) {
> +        if (aiocb->aio_type & QEMU_AIO_WRITE) {
> +            return -EINVAL;
> +        } else {
> +            iov_memset(aiocb->io.iov, aiocb->io.niov, nbytes,
> +                      0, aiocb->aio_nbytes - nbytes);
> +            return aiocb->aio_nbytes;

While reviewing Eric's patches, I noticed that this should be return 0.
Fixing it in my queue.

Kevin

  reply	other threads:[~2018-11-15 16:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31 21:56 [Qemu-devel] [PATCH 00/12] file-posix: Simplify delegation to worker thread Kevin Wolf
2018-10-31 21:56 ` [Qemu-devel] [PATCH 01/12] file-posix: Reorganise RawPosixAIOData Kevin Wolf
2018-10-31 21:56 ` [Qemu-devel] [PATCH 02/12] file-posix: Factor out raw_thread_pool_submit() Kevin Wolf
2018-10-31 21:56 ` [Qemu-devel] [PATCH 03/12] file-posix: Avoid aio_worker() for QEMU_AIO_TRUNCATE Kevin Wolf
2018-10-31 21:56 ` [Qemu-devel] [PATCH 04/12] file-posix: Avoid aio_worker() for QEMU_AIO_COPY_RANGE Kevin Wolf
2018-10-31 21:56 ` [Qemu-devel] [PATCH 05/12] file-posix: Avoid aio_worker() for QEMU_AIO_WRITE_ZEROES Kevin Wolf
2018-10-31 21:56 ` [Qemu-devel] [PATCH 06/12] file-posix: Avoid aio_worker() for QEMU_AIO_DISCARD Kevin Wolf
2018-10-31 21:56 ` [Qemu-devel] [PATCH 07/12] file-posix: Avoid aio_worker() for QEMU_AIO_FLUSH Kevin Wolf
2018-10-31 21:56 ` [Qemu-devel] [PATCH 08/12] file-posix: Move read/write operation logic out of aio_worker() Kevin Wolf
2018-11-15 16:17   ` Kevin Wolf [this message]
2018-10-31 21:56 ` [Qemu-devel] [PATCH 09/12] file-posix: Avoid aio_worker() for QEMU_AIO_READ/WRITE Kevin Wolf
2018-10-31 21:56 ` [Qemu-devel] [PATCH 10/12] file-posix: Remove paio_submit_co() Kevin Wolf
2018-10-31 21:56 ` [Qemu-devel] [PATCH 11/12] file-posix: Switch to .bdrv_co_ioctl Kevin Wolf
2018-10-31 21:56 ` [Qemu-devel] [PATCH 12/12] file-posix: Avoid aio_worker() for QEMU_AIO_IOCTL Kevin Wolf
2018-11-02 12:34 ` [Qemu-devel] [PATCH 00/12] file-posix: Simplify delegation to worker thread no-reply
2018-11-12 16:50 ` Kevin Wolf
2018-11-15 15:26   ` [Qemu-devel] [Qemu-block] " Kevin Wolf

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=20181115161756.GE12677@localhost.localdomain \
    --to=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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 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).