The rapid growth of io_uring [LWN.net]

The rapid growth of io_uring

Posted Jan 30, 2020 14:39 UTC (Thu) by Baughn (subscriber, #124425)
In reply to: The rapid growth of io_uring by Karellen
Parent article: The rapid growth of io_uring

The call fails, and you get to fix your code. The IDs should be per-process.

to post comments

The rapid growth of io_uring

Posted Jan 30, 2020 23:51 UTC (Thu) by Karellen (subscriber, #67644) [Link] (2 responses)

Fix your code? But...

Even per-process, how do you know which fds are free?

Are you suggesting that you should enumerate all the fds currently in use by your program, and then make sure to pick one that you know isn't being used, and hope that another thread doesn't race you to getting it anyway?

Sorry, I think I'm missing an important part of the puzzle somewhere here.

The rapid growth of io_uring

Posted Jan 31, 2020 10:39 UTC (Fri) by klempner (subscriber, #69940) [Link]

You would presumably use an allocator for this, perhaps one that is part of libc.

That allocator wouldn't allocate the same fd twice without a deallocate and could be made threadsafe so you wouldn't have race issues.

The rapid growth of io_uring

Posted Feb 6, 2020 17:26 UTC (Thu) by Wol (subscriber, #4433) [Link]

> Even per-process, how do you know which fds are free?

Run FORTRAN???

That's the way that always worked :-)

Cheers,
Wol