From: "Carter Li 李通洲" <[email protected]>
To: io-uring <[email protected]>
Subject: Short read handling inconsistency for IOSQE_IO_LINK
Date: Fri, 25 Sep 2020 09:37:02 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
Hi all,
Short read of IORING_OP_READ in a link chain is considered an error, because it
will break READ-WRITE chain, which is good.
The problems are:
1. Short read of IORING_OP_RECV in a link chain is *NOT* considered an error,
which is odd and not consistant with IORING_OP_READ. Is it a bug or by design?
2. Short read of IORING_OP_SPLICE in a link chain is considered an error. It is
consistant with IORING_OP_READ, but not very useful because the link
1) splice(fd1, NULL, pfd1, NULL, -1, 0)
2) splice(pfd2, NULL, fd2, NULL, -1, 0)
is a valid operation since the kernel knows how much data can be read in a pipe.
Any thoughts?
Regards,
Carter
reply other threads:[~2020-09-25 9:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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] \
/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