From: Jens Axboe <[email protected]>
To: Dmitry Sychov <[email protected]>, [email protected]
Subject: Re: Waiting for requests completions from multiple threads
Date: Tue, 21 Jan 2020 19:51:00 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CADPKF+ew9UEcpmo-pwiVqiLS5SK2ZHd0ApOqhqG1+BfgBaK5MQ@mail.gmail.com>
On 1/21/20 7:45 PM, Dmitry Sychov wrote:
> Really nice work, I have a question though.
>
> It is possible to efficiently wait for request completions
> from multiple threads?
>
> Like, two threads are entering
> " io_uring_enter" both with min_complete=1 while the completion ring
> holds 2 events - will the first one goes to thread 1 and the second
> one to thread 2?
>
> I just do not understand exactly the best way to scale this api into
> multiple threads... with IOCP for example is is perfectly clear.
You can have two threads waiting on events, and yes, if they each ask to
wait for 1 event and 2 completes, then they will both get woken up. But
the wait side doesn't give you any events, it merely tells you of the
availability of them. When each thread is woken up and goes back to
userspace, it'll have to reap an event from the ring. If each thread
reaps one event from the CQ ring, then you're done.
You need synchronization on the CQ ring side in userspace if you want
two rings to access the CQ ring. That is not needed for entering the
kernel, only when the application reads a CQE (or modifies the ring), if
you can have more than one thread modifying the CQ ring. The exact same
is true on the SQ ring side.
--
Jens Axboe
next prev parent reply other threads:[~2020-01-22 2:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 2:45 Waiting for requests completions from multiple threads Dmitry Sychov
2020-01-22 2:51 ` Jens Axboe [this message]
2020-01-22 3:09 ` Dmitry Sychov
2020-01-22 3:16 ` Jens Axboe
2020-01-22 3:28 ` Pavel Begunkov
2020-01-22 17:54 ` Dmitry Sychov
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