linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>,
	io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH liburing] Test wait after under-consuming
Date: Fri, 13 Dec 2019 11:41:35 +0300	[thread overview]
Message-ID: <688ff2e6-0bb3-908f-5b5f-af894ed9f0c5@gmail.com> (raw)
In-Reply-To: <e5579bbac4fcb4f0e9b6ba4fbf3a56bd9a925c6c.1576224356.git.asml.silence@gmail.com>

On 12/13/2019 11:06 AM, Pavel Begunkov wrote:
> In case of an error submission won't consume all sqes. This tests that
> it will get back to the userspace even if (to_submit == to_wait)
> 
> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
> ---
>  test/link.c | 56 ++++++++++++++++++++++++++++++++++++++++++++++++++++-
>  1 file changed, 55 insertions(+), 1 deletion(-)
> 
> diff --git a/test/link.c b/test/link.c
> index 8ec1649..93653f3 100644
> --- a/test/link.c
> +++ b/test/link.c
> @@ -384,6 +384,55 @@ err:
>  	return 1;
>  }
>  
> +static int test_early_fail_and_wait(struct io_uring *ring)
> +{
> +	struct io_uring_cqe *cqe;
> +	struct io_uring_sqe *sqe;
> +	int ret, submitted, i;
> +	const int invalid_fd = 42;
> +	struct iovec iov = { .iov_base = NULL, .iov_len = 0 };
> +
> +	sqe = io_uring_get_sqe(ring);
> +	if (!sqe) {
> +		printf("get sqe failed\n");
> +		goto err;
> +	}
> +
> +	io_uring_prep_readv(sqe, invalid_fd, &iov, 1, 0);
> +	sqe->user_data = 1;
> +	sqe->flags |= IOSQE_IO_LINK;
> +
> +	sqe = io_uring_get_sqe(ring);
> +	if (!sqe) {
> +		printf("get sqe failed\n");
> +		goto err;
> +	}
> +
> +	io_uring_prep_nop(sqe);
> +	sqe->user_data = 2;
> +
> +	submitted = io_uring_submit_and_wait(ring, 2);
> +	if (submitted == -EAGAIN)
> +		return 0;

As io_uring isn't recreated for each test case, I need to complete all
cqes in any case. I'll resend

> +	if (submitted <= 0) {
> +		printf("sqe submit failed: %d\n", submitted);
> +		goto err;
> +	}
> +
> +	for (i = 0; i < 2; i++) {
> +		ret = io_uring_wait_cqe(ring, &cqe);
> +		if (ret < 0) {
> +			printf("wait completion %d\n", ret);
> +			goto err;
> +		}
> +		io_uring_cqe_seen(ring, cqe);
> +	}
> +
> +	return 0;
> +err:
> +	return 1;
> +}
> +
>  int main(int argc, char *argv[])
>  {
>  	struct io_uring ring, poll_ring;
> @@ -400,7 +449,6 @@ int main(int argc, char *argv[])
>  	if (ret) {
>  		printf("poll_ring setup failed\n");
>  		return 1;
> -
>  	}
>  
>  	ret = test_single_link(&ring);
> @@ -439,5 +487,11 @@ int main(int argc, char *argv[])
>  		return ret;
>  	}
>  
> +	ret = test_early_fail_and_wait(&ring);
> +	if (ret) {
> +		fprintf(stderr, "test_early_fail_and_wait\n");
> +		return ret;
> +	}
> +
>  	return 0;
>  }
> 

-- 
Pavel Begunkov

  reply	other threads:[~2019-12-13  8:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-13  8:06 [PATCH liburing] Test wait after under-consuming Pavel Begunkov
2019-12-13  8:41 ` Pavel Begunkov [this message]
2019-12-13 17:11 ` [PATCH v2 " Pavel Begunkov
2019-12-13 18:41   ` 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 \
    --in-reply-to=688ff2e6-0bb3-908f-5b5f-af894ed9f0c5@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).