From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [PATCH liburing v5 2/2] test/splice: add basic splice tests
Date: Mon, 24 Feb 2020 11:23:05 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <aa79d4a192bd1a8e68beddfb177618c1cdacf381.1582566728.git.asml.silence@gmail.com>
On 2/24/20 10:55 AM, Pavel Begunkov wrote:
> +static int copy_single(struct io_uring *ring,
> + int fd_in, loff_t off_in,
> + int fd_out, loff_t off_out,
> + int pipe_fds[2],
> + unsigned int len,
> + unsigned flags1, unsigned flags2)
> +{
> + struct io_uring_cqe *cqe;
> + struct io_uring_sqe *sqe;
> + int i, ret = -1;
> +
> + sqe = io_uring_get_sqe(ring);
> + if (!sqe) {
> + fprintf(stderr, "get sqe failed\n");
> + return -1;
> + }
> + io_uring_prep_splice(sqe, fd_in, off_in, pipe_fds[1], -1,
> + len, flags1);
> + sqe->flags = IOSQE_IO_LINK;
> +
> + sqe = io_uring_get_sqe(ring);
> + if (!sqe) {
> + fprintf(stderr, "get sqe failed\n");
> + return -1;
> + }
> + io_uring_prep_splice(sqe, pipe_fds[0], -1, fd_out, off_out,
> + len, flags2);
> +
> + ret = io_uring_submit(ring);
> + if (ret <= 1) {
> + fprintf(stderr, "sqe submit failed: %d\n", ret);
> + return -1;
> + }
This seems wrong, you prep one and submit, the right return value would
be 1. This check should be < 1, not <= 1. I'll make the change, rest
looks good to me. Thanks!
--
Jens Axboe
next prev parent reply other threads:[~2020-02-24 18:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 17:54 [PATCH v5 0/2] splice helpers + tests Pavel Begunkov
2020-02-24 17:55 ` [PATCH liburing v5 1/2] splice: add splice(2) helpers Pavel Begunkov
2020-02-24 17:55 ` [PATCH liburing v5 2/2] test/splice: add basic splice tests Pavel Begunkov
2020-02-24 18:23 ` Jens Axboe [this message]
2020-02-24 18:26 ` Pavel Begunkov
2020-02-24 18:33 ` Jens Axboe
2020-02-24 18:39 ` Pavel Begunkov
2020-02-24 18:41 ` Jens Axboe
2020-02-24 18:47 ` Pavel Begunkov
2020-02-24 19:30 ` Jens Axboe
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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