Browse Prior Art Database

System and method of Virtual Machine transparent I/O caching at hypervisor layer

IP.com Disclosure Number: IPCOM000239799D
Publication Date: 2014-Dec-02
Document File: 5 page(s) / 360K

Publishing Venue

The IP.com Prior Art Database

Related People

Shirish Vijayvargiya: INVENTOR [+3]

Abstract

System and method of performing Virtual Machine transparent I/O caching at the hypervisor layer by deriving hints from the either understanding the layout of data on each of the virtual disk to statically determine the I/O pattern or having an active entity in the virtual machine which can dynamically detect the I/O pattern and employing different caching mode/policies.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 33% of the total text.

Page 01 of 5

System and method of Virtual Machine transparent I/O caching at hypervisor layer

  Sanjay Kumar Hari Krishna Vemuri

Shirish Vijayvargiya

Symantec Corporation

Abstract

System and method of performing Virtual Machine transparent I/O caching at the hypervisor layer by deriving hints from the either understanding the layout of data on each of the virtual disk to statically determine the I/O pattern or having an active entity in the virtual machine which can dynamically detect the I/O pattern and employing different caching mode/policies.

Copyright © 2014 Symantec Corporation. All rights reserved. 1


Page 02 of 5

Copyright © 2014 Symantec Corporation. All rights reserved. Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. For a full list of Symantec trademarks, please visit http://www.symantec.com/about/profile/policies/trademarks/currentlist.jsp

Any Symantec products described in this document are distributed under licenses restricting their use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

Symantec Corporation 350 Ellis Street Mountain View, CA 94043 United States

http://www.symantec.com

Copyright © 2014 Symantec Corporation. All rights reserved. 2


Page 03 of 5

Problem Statement

In VM-aware Caching (vFlash Memory), a SSD is directly allocated to virtual machine (VM) and caching algorithm can be controlled within the guest, not by the caching software on the hypervisor. In VM- transparent caching, cache software on the hypervisor is there to provide a suitable algorithm to cache I/O. In latter type of caching, the algorithm of caching would be fixed for each block read or written from/to virtual disk file. For example below types of operations could be possible on each IO with respect to SSD on the Host:


1. Write on SSD and HDD. Both in sync. (write-through)

2. Write on SSD with sync and then on HDD async (write-back)

3. First read from SSD, if not found go to HDD and cache it to SSD (read-through)

4. Only write on to SSD, not on HDD (temporary caching)

5. Only write on HDD, not on SSD (no caching)

6. Write to only low cost SSD type (MLC) for static data if multiple types of S...