FileDescriptor.sync isn't using Blocker

Alan Bateman Alan.Bateman at oracle.com
Thu Jul 13 18:10:11 UTC 2023


On 13/07/2023 18:10, Cay Horstmann wrote:
> I found it hard to tell from the JEP what happens in such a case.
>
> "However, some blocking operations in the JDK do not unmount the 
> virtual thread, and thus block both its carrier and the underlying OS 
> thread. This is because of limitations at either the OS level (e.g., 
> many filesystem operations) or the JDK level (e.g., Object.wait()). 
> The implementations of these blocking operations compensate for the 
> capture of the OS thread by temporarily expanding the parallelism of 
> the scheduler."
>
> But later:
>
> "The scheduler does not compensate for pinning by expanding its 
> parallelism."
>
> Am I missing some subtlety here?

The last part of this section is introduced with "There are two 
scenarios ..." and these are the two scenarios where the scheduler 
doesn't compensate. Maybe nested sub-sections would be better here but 
the text is otherwise correct.

-Alan



More information about the loom-dev mailing list