Implementation of AsynchronousFileChannel using io_uring API

[Andrey Lomakin]

Alan, would you mind answering the additional questions.

Does the current version of Loom project prevent thread pining if I use
FileChannel?

On Thu, Nov 18, 2021 at 10:08 AM Andrey Lomakin <lomakin.andrey at gmail.com>
wrote:

> Hi Alan.
> Thank you for providing the update.
>
> I am not so interested in whether it will be Async or classic file channel
> as the fact that implementation will not suffer from thread pinning and
> will use OS mechanics as much as possible.
> Looking forward to seeing those changes in upcoming releases :-)
>
>
>
> On Thu, Nov 18, 2021 at 10:02 AM Alan Bateman <Alan.Bateman at oracle.com>
> wrote:
>
>> On 18/11/2021 06:33, Andrey Lomakin wrote:
>> > Hi guys.
>> > The article described the state of the project Loom announced plans to
>> > implement AsynchronousFileChannel using io_uring API.
>> > Unfortunately, I did not find any further information about the state of
>> > this implementation.
>> > Could you provide an update on whether such implementation was
>> completed?
>> I suspect this is the "State of Loom", May 2020 edition, is that right?
>> For buffered file I/O it outlines two phases, short term to compensate
>> for the pinning, later to make use of OS mechanism where possible. So
>> yes, the intention is to come back to an io_uring implementation of
>> FileChannel and java.io, just not in the first release.
>> AsynchronousFileChannel provides an async API so not directly
>> interesting to this project. It could potentially be re-implemented
>> using io_uring, independent of this project. The draft JEP for virtual
>> threads [1] has a work-in-progress summary of the core of a possible
>> first release.
>>
>> -Alan
>>
>> [1] https://openjdk.java.net/jeps/8277131
>>
>
>
> --
> Best regards,
> Andrey Lomakin.
>
>

-- 
Best regards,
Andrey Lomakin.