This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/25829] [F03] Asynchronous IO support


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25829

--- Comment #33 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
(In reply to Janne Blomqvist from comment #32)
> Interestingly, Linux 4.14 contains a way to avoid a context switch to a
> threadpool in case the data is already in the page cache:
> https://kernelnewbies.org/Linux_4.14#head-
> 8c8861fbded3e87631ab06bcd511f5f0d8bfa220
> 
> Might be an interesting optimization sometime in the future..

It is interesting that I was reading this very webpage myself today looking at
4.14 feature. I am pretty sure we can hand off the I/O to the OS. I am not so
sure how one checks the status of the operaton. This is what wait should do,
wait for completion.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]