winapi - Question about hard drive , 'seek' and 'read' in windows OS -


Do anyone know how to physically influence the hard drive when called 'search' and 'read' is?

If I would be more specific, then I know that there is any type of magnetic needle in the hard drive that is used to read data from magnetic plates. So my question is, when the needle actually goes to the place of reading?

Is this window when we are calling the "app" window API method (no real read launch), or "remember" just a virtual pointer, and the physical speed of the needle only What happens when the "reading" method is called?

Edit : Assume that the hard-to-be-requested data -Drive is not present in any cache (hard drive cache, OS cache, RAM and whatever may be)

wanted to break this post from your post

When the needle Actually goes to the place of reading?

I think the simple answer is "whenever the data is requested that it is not already present in any cache" the problem with the prediction of the hard drive movement is that you All the different places to consider that cache the data read from the hard drive. If the data is present in those caches and is accessible in the context of data requests, then in reality the cache will be used instead of reading the hard drive. Here are some places that can cache hard drive data

  • Internal cache of hard drive
  • OS level cache
  • Program level cache
  • API level cache

In a situation where no data exists, it will probably be read from the hard drive during read . . The reason for a search call is not due to the hard drive being transferred because you are not changing the physical hard drive indicator, but the virtual pointer in the file inside your program


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -