From: Pavel Begunkov <[email protected]>
To: hexue <[email protected]>, [email protected]
Cc: [email protected], [email protected]
Subject: Re: [PATCH liburing] test: add test cases for hybrid iopoll
Date: Wed, 13 Nov 2024 03:32:08 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 11/11/24 12:36, hexue wrote:
> Add a test file for hybrid iopoll to make sure it works safe.Testcass
> include basic read/write tests, and run in normal iopoll mode and
> passthrough mode respectively.
>
> Signed-off-by: hexue <[email protected]>
If it's not covered already please add tests for failure cases.
E.g. when SETUP_HYBRID_IOPOLL is set without SETUP_IOPOLL
> +static int test_io_uring_passthrough(const char *file, int tc, int write, int sqthread,
> + int fixed, int nonvec)
> +{
> + struct io_uring ring;
> + int ret, ring_flags = 0;
> +
> + ring_flags |= IORING_SETUP_SQE128;
> + ring_flags |= IORING_SETUP_CQE32;
> + ring_flags |= IORING_SETUP_HYBRID_IOPOLL;
> +
> + if (sqthread)
> + ring_flags |= IORING_SETUP_SQPOLL;
Doesn't it also need IORING_SETUP_IOPOLL?
> +
> + ret = t_create_ring(64, &ring, ring_flags);
> + if (ret == T_SETUP_SKIP)
> + return 0;
> + if (ret != T_SETUP_OK) {
> + if (ret == -EINVAL) {
> + no_pt = 1;
> + return T_SETUP_SKIP;
> + }
> + fprintf(stderr, "ring create failed: %d\n", ret);
> + return 1;
> + }
> +
> + ret = __test_io_uring_passthrough_io(file, &ring, tc, write, sqthread, fixed, nonvec);
> + io_uring_queue_exit(&ring);
> +
> + return ret;
> +}
--
Pavel Begunkov
next prev parent reply other threads:[~2024-11-13 3:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241111123656epcas5p20cac863708cd83d1fdbb523625665273@epcas5p2.samsung.com>
2024-11-11 12:36 ` [PATCH liburing] test: add test cases for hybrid iopoll hexue
2024-11-12 10:44 ` Anuj Gupta
2024-11-12 15:43 ` Jens Axboe
[not found] ` <CGME20241113062730epcas5p10bec3fe462b9b6e65d22a61c50902b78@epcas5p1.samsung.com>
2024-11-13 6:27 ` hexue
[not found] ` <CGME20241113062658epcas5p3d7234648ac86e7a16dab96c3c1d5dc98@epcas5p3.samsung.com>
2024-11-13 6:26 ` hexue
2024-11-13 3:32 ` Pavel Begunkov [this message]
[not found] ` <CGME20241113062517epcas5p22b01ddf9f29123ddcd7ffc63f2ce9254@epcas5p2.samsung.com>
2024-11-13 6:25 ` hexue
2024-11-14 15:21 [PATCH liburing v2] " Jens Axboe
[not found] ` <CGME20241115033450epcas5p10bdbbfa584b483d8822535d43da868d2@epcas5p1.samsung.com>
2024-11-15 3:34 ` Re: [PATCH liburing] " hexue
2024-11-15 15:40 ` 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] \
[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