Re: Making Lemonade (Floating-point format changes)

EricP wrote:

MitchAlsup1 wrote:

EricP wrote:
 

MitchAlsup1 wrote:

Scott Lurndal wrote:
>

I would want an option in this SR-IOV mechanism for the guest app to
tell the guest OS to tell the HV to pin the buffer before starting IO.

   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.

I don't understand your question.

Most of users files are on the local system and SR-IOV works fine, but one
or more of his files exist on a remote machine accessed over the internet;
and user still uses SR-IOV interface to access those files.
How does the system provide the "file is local" illusion to a user having
SR-IOV access to a non-local file.
For example, user opens a file which is an ln-s (a block containing a URL to where the file is remotely stored) but user thinks file is local.