From: Pavel Begunkov <[email protected]>
To: [email protected]
Cc: Jens Axboe <[email protected]>, [email protected]
Subject: [PATCH liburing 6/7] tests/send: improve error reporting
Date: Tue, 21 Feb 2023 01:05:57 +0000 [thread overview]
Message-ID: <077207aff1e31d30bdcdacbb6b0379d24798cea9.1676941370.git.asml.silence@gmail.com> (raw)
In-Reply-To: <[email protected]>
Signed-off-by: Pavel Begunkov <[email protected]>
---
test/send-zerocopy.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/test/send-zerocopy.c b/test/send-zerocopy.c
index 481aa28..8ddec39 100644
--- a/test/send-zerocopy.c
+++ b/test/send-zerocopy.c
@@ -447,7 +447,8 @@ static int do_test_inet_send(struct io_uring *ring, int sock_client, int sock_se
}
if (cqe->user_data == RX_TAG) {
if (cqe->res != send_size) {
- fprintf(stderr, "rx failed %i\n", cqe->res);
+ fprintf(stderr, "rx failed res: %i, expected %i\n",
+ cqe->res, (int)send_size);
return 1;
}
io_uring_cqe_seen(ring, cqe);
--
2.39.1
next prev parent reply other threads:[~2023-02-21 1:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 1:05 [PATCH liburing 0/7] test sends with huge pages Pavel Begunkov
2023-02-21 1:05 ` [PATCH liburing 1/7] tests/send: don't use a constant for page size Pavel Begunkov
2023-02-21 1:05 ` [PATCH liburing 2/7] send: improve buffer iteration Pavel Begunkov
2023-02-21 1:05 ` [PATCH liburing 3/7] send: test send with hugetlb Pavel Begunkov
2023-02-21 1:05 ` [PATCH liburing 4/7] examples/zc: add a hugetlb option Pavel Begunkov
2023-02-21 1:05 ` [PATCH liburing 5/7] test/send: don't use SO_ZEROCOPY if not available Pavel Begunkov
2023-02-21 1:05 ` Pavel Begunkov [this message]
2023-02-21 1:05 ` [PATCH liburing 7/7] tests/send: sends with offsets Pavel Begunkov
2023-02-22 16:54 ` [PATCH liburing 0/7] test sends with huge pages 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=077207aff1e31d30bdcdacbb6b0379d24798cea9.1676941370.git.asml.silence@gmail.com \
[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