From: Josef <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: wake up io_uring_enter(...IORING_ENTER_GETEVENTS..) via eventfd
Date: Fri, 7 Aug 2020 10:17:13 +0200 [thread overview]
Message-ID: <CAAss7+rbm8D8OyM1gjj7wXCizVPeGxh19WUOiiX3bzcqe4v2zQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
Hi,
yeah thanks, there is already a fix patch from Jens [PATCH] io_uring:
use TWA_SIGNAL for task_work related to eventfd
On Fri, 7 Aug 2020 at 09:31, Pavel Begunkov <[email protected]> wrote:
>
> Hi,
>
> I'd love to help but don't have time at the moment. I'll take a look but
> in a week, either send it to [email protected]. Jens deals with
> such stuff lightning fast!
>
> > io_uring application should be a single thread in my application which
> > means a different thread wakes up io_uring_enter via eventfd. The issue is
> > that io_uring_enter(fd, 0, min_complete, IORING_ENTER_GETEVENTS, 0) which
> > is blocking doesn't get any poling event from eventfd_write when both
> > functions are executed in different threads
>
> Yeah, sounds strange. Did you try to do the same but without io_uring?
> e.g. with write(2), select(2).
>
> >
> >
> > here small example
> >
> > https://gist.github.com/1Jo1/6496d1b8b6b363c301271340e2eab95b
> >
> >
> > io_uring_enter will get a polling event if you move eventfd_write(efd,
> > (eventfd_t) 1L) to the main thread,
> >
> > I don't get it..probably I missed something, why can't I run both functions
> > on different threads, any ideas what the cause might be?
> >
> >
> > (Linux Kernel 5.7.10-201) liburing 0.6 & 0.7
> >
> > ---
> > Josef
> >
>
> --
> Pavel Begunkov
prev parent reply other threads:[~2020-08-07 8:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAss7+rhVS669Q=PCHrmHXbr067HpdC7Dtu0ogm4u-uj6-qK3Q@mail.gmail.com>
2020-08-07 7:29 ` wake up io_uring_enter(...IORING_ENTER_GETEVENTS..) via eventfd Pavel Begunkov
2020-08-07 8:17 ` Josef [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=CAAss7+rbm8D8OyM1gjj7wXCizVPeGxh19WUOiiX3bzcqe4v2zQ@mail.gmail.com \
[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