Re: Making Lemonade (Floating-point format changes)

On 5/18/2024 6:40 AM, EricP wrote:

Chris M. Thomasson wrote:

On 5/17/2024 12:26 PM, EricP wrote:

MitchAlsup1 wrote:

>
So, what happens if GuestOS thinks the user file is located on a local
SATA drive, but it is really across some network ?? This works when devices are not virtualized since the request is routed to a different
system where the file is local, accessed and data returned over the
network.
>
Does this mean the application has lost a level of indirection in order
to have become virtualized ?????

>
I don't understand your question.
My comment was about the consequences of not pinning buffer pages
before starting an I/O. If those pages were for a mapped file stored
on a network device it won't be different.

>
For some reason this made me think about getting a blue screen of death due to too much non-paged memory being used by too many concurrent overlapped IO's on Windows.

 That shouldn't happen as Windows tracks each process's non-paged pool
allocations and quotas and it should return an error when exceeded,
though I've never stress tested it.
 

I have, wrt NT 4.0 back in the day. It can get to a point where the system is totally unresponsive. Then, sometimes, dies. A shit load of concurrent overlapped io ops, malloc tends to return NULL, then the non-paged memory gets really bad...