Method and system for sharing driver pages

• US 10,216,529 B1
• Filed: 11/19/2015
• Issued: 02/26/2019
• Est. Priority Date: 11/19/2015
• Status: Active Grant

• Current Assignee: Virtuozzo International GmbH
• Original Assignee: Virtuozzo International GmbH
• Inventors: Makhov, Pavel, Kudinova, Marina, Kostyushko, Alexey, Philippov, Mikhail
• Primary Examiner(s): Birkhimer, Christopher D
• Application Number:
  US14/945,678
• Time in Patent Office: 1,195 Days
• CPC Class Codes: G06F 12/023 Free address space management
• CPC Class Codes: G06F 12/10 Address translation
• CPC Class Codes: G06F 12/1009 using page tables, e.g. page table structures
• CPC Class Codes: G06F 12/109 for multiple virtual address spaces, e.g. segmentation G06F12/1036 takes precedence
• CPC Class Codes: G06F 12/126 with special data handling, e.g. priority of data or instructions, handling errors or pinning
• CPC Class Codes: G06F 12/1441 for a range
• CPC Class Codes: G06F 2212/1032 Reliability improvement, data loss prevention, degraded operation etc
• CPC Class Codes: G06F 2212/1044 Space efficiency improvement
• CPC Class Codes: G06F 2212/655 Same page detection
• CPC Class Codes: G06F 2212/656 Address space sharing
• CPC Class Codes: G06F 2212/657 Virtual address space management
• CPC Class Codes: G06F 9/4411 Configuring for operating with peripheral devices; Loading of device drivers
• CPC Class Codes: G06F 9/44563 Sharing
• CPC Class Codes: G06F 9/455 Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines

Abstract

Method for sharing driver pages, including, on a computer system having a first driver and performing system services, instantiating Containers; code and data of the driver are loaded sequentially into pages arranged in a virtual memory, and instantiating a next driver upon a request from one of the Containers for system services by: loading physical pages of the next driver into physical memory and allocated virtual memory pages for the next driver; associating the next driver with the first driver and comparing pages of the next driver and the first driver, generating a set of identical physical pages; mapping virtual pages of the next driver to identical physical pages of the first driver while atomically protecting identical physical pages; non-identical pages of the next driver from physical memory remain mapped to virtual pages of the next driver; releasing physical memory occupied by identical physical pages of the next driver.

Claims

1. A computer-implemented method for sharing driver pages among Containers, the method comprising:

on a computer system having a processor, a single operating system (OS) and a first instance of a dedicated system driver installed and performing dedicated system services, instantiating a plurality of Containers that virtualize the OS, wherein code and data of the first instance of the dedicated system driver are loaded from an image into a plurality of pages arranged in a virtual memory, and

instantiating a second instance of the dedicated system driver upon a first request from one of the Containers for dedicated system services by;

(a) loading, from the image, pages of the second instance into a physical memory and allocating virtual memory pages for the second instance;

(b) associating the second instance with the first instance and acquiring virtual addresses of identical pages of the first instance compared to the second instance;

(c) mapping the virtual addresses of the identical pages of the second instance to physical pages to which virtual addresses of the corresponding identical pages of the first instance are mapped, while protecting the physical pages from modification;

(d) wherein virtual addresses of non-identical pages of the second instance remain mapped to the physical pages of the second instance;

(e) releasing the physical memory occupied by the identical physical pages of the second instance; and

(f) starting the second instance for responding to requests for the dedicated system services from the one of the Containers.

2. The method of claim 1, further comprising performing steps (a)-(f) for a subsequent driver and another Container.

3. The method of claim 1, further comprising performing steps (a)-(f) for a subsequent driver of the one of the Containers.

4. The method of claim 1, wherein the first instance is installed and started in the one of the Containers upon a request from a user.

5. The method of claim 1, wherein the identical pages of the first instance are write-protected and identical pages of the second instance are mapped to the corresponding physical pages of the first instance.

6. The method of claim 1, wherein the first instance is located in the operating system.

7. The method of claim 1, wherein the first instance is located in the one of the containers.

8. The method of claim 1, further comprising:

when the first instance is loading, creating a set of physical pages that do not belong to any of the drivers, wherein;

(a) the identical pages of the first instance are remapped to the physical pages of the set of physical pages;

(b) the physical memory occupied by the identical physical pages of the first instance is released; and

when the second instance is loading;

(c) the identical pages of the second instance are mapped to the physical pages of the set of physical pages;

(d) the physical memory occupied by the identical physical pages of the second instance is released.

9. The method of claim 1, wherein when the second instance is loading, identical pages of the second instance are directly mapped to the physical pages, to which virtual addresses of the corresponding identical pages of the first instance are mapped and no physical memory is allocated for the identical pages of the second instance.

10. The method of claim 9, further comprising intercepting driver loading and unloading to perform a cleanup of the mapped pages and allocating a random accessed memory for any private and the identical physical pages by a memory manager.

11. The method of claim 1, further comprising creating the driver database which contains information about which pages of which driver are identical and the Container-specific settings including driver name, registry parameters and file parameters.

12. The method of claim 1, further comprising loading the second instance from a driver database.

13. The method of claim 1, wherein a match of the first instance and the second instance is checked by comparing pages of the second instance to the pages of the first instance.

14. The method of claim 1, wherein a match of the first instance and the second instance is checked using information about any of name, version, and driver checksum.

15. The method of claim 1, wherein a match of the first instance and the second instance is checked using information stored in a driver database.

16. The method of claim 1, wherein the acquiring of the virtual addresses of the identical driver pages is done by comparing pages of the second instance to the pages of the first instance.

17. The method of claim 1, wherein the acquiring of the virtual addresses of the identical driver pages is done using information about driver sections.

18. The method of claim 1, wherein the acquiring of the virtual addresses of the identical driver pages is done using information stored in driver database.

19. The method of claim 1, further comprising enumerating the second instance prior to loading it into the Container by assigning a unique number to the second instance.

20. The method of claim 18, further comprising changing names of any instances of the dedicated system driver so that each Container has a driver with a unique name.

21. The method of claim 1, wherein the identical physical pages are not modifiable by any process and are shared among the plurality of Containers.

22. The method of claim 1, wherein the non-identical pages are private pages that store data of the one of the Containers.

23. The method of claim 1, wherein each Container can modify its own private pages, but not the physical pages that are shared among the plurality of the Containers.

24. The method of claim 22, wherein on attempt to modify any shared page by any instance of the dedicated system driver:

a new physical page is allocated;

contents of a corresponding shared page are copied to a newly allocated physical page; and

a virtual address of the driver page is remapped to the newly allocated physical page.

25. The method of claim 1, further comprising generating:

(a) a reserve buffer which is a set of pre-allocated pages used for unmerging driver pages if the host OS is unable to provide pages immediately;

(b) a special monitoring system, which ensures that this buffer is never out of pages.

26. The method of claim 1, wherein the identical pages are locked in the memory and are not swappable to a disk.

27. The method of claim 1, wherein the non-identical pages are locked in the memory and are not swappable to a disk.

28. The method of claim 1, wherein when a driver is unloaded, only non-identical pages are released.

29. The method of claim 28, wherein stopping the driver being unloaded includes:

(a) allocating physical memory equal to the set of identical physical pages;

(b) remapping the virtual memory pages to the newly allocated memory;

(c) unloading the driver from the one of the Containers and the OS;

(d) freeing up the allocated memory and the memory occupied by the non-identical pages.

30. The method of claim 28, wherein virtual addresses of the identical pages of the driver are marked as already unloaded.

31. The method of claim 28, wherein the new physical pages are taken from the set of pre-allocated pages.

32. The method of claim 28, wherein, when the last instance of the dedicated system driver is unloaded from system, all allocated memory is released.

33. A computer-implemented method for sharing driver pages among Containers, the method comprising:

(a) tracking loading and unloading of each instance of a driver in the Containers,

wherein the Containers run on a host with a single Operating System (OS), and wherein the Containers virtualize the OS;

(b) upon a loading of a first instance of the driver, analyzing portions of executable files of the driver to find pages suitable to share (identical), to generate a “

zeroth”

set of pages;

(c) upon loading of a second instance of the driver

checking that the driver is the same as the first driver;

generating a set shared of common pages among the drivers that is the “

zeroth”

set;

substituting the common pages for pages of the second instance of the drivers when the pages are identical;

making virtual writeable pages copy on write; and

returning freed up pages of the drivers back to the system;

(d) upon loading of a third and subsequent instances of the driver

checking that the drivers are the same as the first driver;

substituting the common pages for pages of the drivers when the pages are identical;

making virtual writeable pages copy on write;

returning freed up pages of the drivers back to the system;

(e) during system operation, upon a write attempt to a common page, unmerging that page of the driver from the common page set;

(f) upon unloading of one of the instances of the driver, unmerging the pages of the instance of the driver being unloaded; and

(g) upon unloading of the last instance of the driver, deleting the “

zeroth”

set of pages.