From: Jens Axboe <[email protected]>
To: [email protected], [email protected]
Subject: Re: SQPOLL behaviour with openat
Date: Sat, 4 Jan 2020 09:28:08 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 1/4/20 9:22 AM, [email protected] wrote:
> Hello,
>
> I am trying to understand SQPOLL behaviour using liburing. I modified the
> test in liburing (see below). The test is failing when we use `openat`
> with SQPOLL:
>
> cqe res -9
> test_io failed 0/0/1/0/0
>
> Is `openat` supported with SQPOLL? If not I would expect -EINVAL as a
> return value, but maybe I'm missing something.
> note: I also tested without io_uring_register_files call.
sqpoll requires the use of fixed files for any sqe, at least for now.
That's why it returns -EBADF if the request doesn't have fixed files
specified.
So it cannot be used with opcodes that create (or close) file
descriptors either.
--
Jens Axboe
next prev parent reply other threads:[~2020-01-04 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 16:22 SQPOLL behaviour with openat wdauchy
2020-01-04 16:28 ` Jens Axboe [this message]
2020-01-04 16:41 ` William Dauchy
2020-01-04 17: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 \
[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