User Tools

Site Tools


developersguide:vmcalls

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
developersguide:vmcalls [2015/09/19 10:44]
dcvmoole [C Interface] the spanish inquisition of VM calls
developersguide:vmcalls [2015/09/19 10:46] (current)
dcvmoole [Logical Interface] update this part as well, why is it even here?
Line 20: Line 20:
 is informational,​ they needn'​t be unique in the VM cache. is informational,​ they needn'​t be unique in the VM cache.
  
-Logically there are three operations:+Logically there are four operations:
  
   - Set a block. The caller passes the virtual address of the block, its length, and its identification to VM. VM will keep that block and the metadata in its cache. This is the way to indicate a new cache block to VM, for possible later retrieval. The ''​(dev,​ dev_off)''​ pair is required and is unique; a possible existing block with that ID will be removed from the cache.   - Set a block. The caller passes the virtual address of the block, its length, and its identification to VM. VM will keep that block and the metadata in its cache. This is the way to indicate a new cache block to VM, for possible later retrieval. The ''​(dev,​ dev_off)''​ pair is required and is unique; a possible existing block with that ID will be removed from the cache.
   - Map a block. The caller passes the ''​(dev,​ dev_off)''​ pair to VM, together with further metadata. If the block exists, VM maps the cache block in and returns the address to the caller. VM updates its notion of the inode and inode offset of the block.   - Map a block. The caller passes the ''​(dev,​ dev_off)''​ pair to VM, together with further metadata. If the block exists, VM maps the cache block in and returns the address to the caller. VM updates its notion of the inode and inode offset of the block.
 +  - Forget a block. The caller passes a ''​(dev,​ dev_off)''​ pair to VM, along with a block size. If the block exists, VM throws it out of the cache.
   - Clear blocks. The caller passes a ''​dev''​ device identifier to VM, and VM removes all blocks associated with that device from its cache.   - Clear blocks. The caller passes a ''​dev''​ device identifier to VM, and VM removes all blocks associated with that device from its cache.
  
developersguide/vmcalls.txt · Last modified: 2015/09/19 10:46 by dcvmoole