Jens Axboe

@alexhultman Please tone down the snark. FWIW, @romange has done plenty of testing in the past, and was instrumental in finding the task work related signal slowdown for threads. Questioning...

@HowHsu By all means go ahead, knee deep in a bunch of other things. Thanks!

Those fixes are in mainline.

@johalun That seems to be a good clue, ```IORING_OP_SPLICE``` is a bit tricky in that where does it go in terms of bound vs unbound, and I'm guessing it ends...

It would be a pretty trivial change to arm poll rather than return -EAGAIN to the application, if O_NONBLOCK is set on the file. The main issue here is how...

As mentioned, that only then works for the read/write variants, not for any other opcode. Hence I'd be leaning towards making it an sqe flag instead. If it was just...

Each opcode has a specific set of flags, like the RWF_* for read/write, but there's also a generic set of IOSQE_* flags that apply to any opcode. That handles things...

I’ll spin a patch tomorrow morning. > On Jun 16, 2021, at 5:56 PM, Samuel Williams ***@***.***> wrote: > >  > Oh that makes total sense. Okay, I'm keen...

Probably something like IOSQE_IGNORE_NONBLOCK or whatever. It'll just be a way to force the normal poll path for pollable IO even if the fd is marked non-blocking.

Here's a first attempt. Let me know if you'd prefer a patch somewhere, not sure what this does to formatting... If it destroys whitespace, probably just use patch -l to...