From: Dmitry Sychov <[email protected]>
To: [email protected]
Subject: Re: Waiting for requests completions from multiple threads
Date: Wed, 22 Jan 2020 20:54:30 +0300 [thread overview]
Message-ID: <CADPKF+fN5fjRETntKVXsbUWhf5thaEyHHQ3cVgtZrLAgF3AUUg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
> Just one thread gets completions (i.e. calls io_uring_enter()), and than distributes
> jobs to a thread pool.
Yep, I'am thinking along this lines - one thread is getting the state update
for multiple events and spreading it to waiting worker threads through
semaphore or else
I assume there is no protection of multiple threads waking up from
single event(one of the
epoll original problems which was fixed with a new flag).
The worker threads are free to submit new job requests directly into
the SQE though(without a proxy job list).
prev parent reply other threads:[~2020-01-22 17:55 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
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 [this message]
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=CADPKF+fN5fjRETntKVXsbUWhf5thaEyHHQ3cVgtZrLAgF3AUUg@mail.gmail.com \
[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