From: Glauber Costa <[email protected]>
To: [email protected], Avi Kivity <[email protected]>,
Jens Axboe <[email protected]>
Subject: how is register_(buffer|file) supposed to work?
Date: Tue, 11 Feb 2020 23:12:22 -0500 [thread overview]
Message-ID: <CAD-J=zbYp0D5NSV1hqxpU7C-Ki+ffwretuXEYCxX5cbazA5WqQ@mail.gmail.com> (raw)
Hi,
I am trying to experiment with the interface for registering files and buffers.
(almost) Every time I call io_uring_register with those opcodes, my
application hangs.
It's easy to see the reason. I am blocking here:
mutex_unlock(&ctx->uring_lock);
ret = wait_for_completion_interruptible(&ctx->completions[0]);
mutex_lock(&ctx->uring_lock);
Am I right in my understanding that this is waiting for everything
that was submitted to complete? Some things in my ring may never
complete: for instance one may be polling for file descriptors that
may never really become ready.
This sounds a bit too restrictive to me. Is this really the intended
use of the interface?
next reply other threads:[~2020-02-12 4:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 4:12 Glauber Costa [this message]
2020-02-12 14:20 ` how is register_(buffer|file) supposed to work? Jens Axboe
2020-02-12 14:23 ` Glauber Costa
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='CAD-J=zbYp0D5NSV1hqxpU7C-Ki+ffwretuXEYCxX5cbazA5WqQ@mail.gmail.com' \
[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