IP Library Granted Patent US 11,016,886
Granted Patent B2
US 11,016,886 · App. 16/791,669 · Granted May 25, 2021

Multi-ring shared, traversable, and dynamic advanced database

Inventor: John R. Shaw, II (Broomfield, CO)
Assignee: WEBROOT INC.
G06F12/0653G06F12/0615G06F12/1491G06F16/00G06F21/00G06F2212/1016G06F2212/1052
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,016,886
App. No.
16/791,669
Granted
May 25, 2021
Kind
B2
Abstract

Examples of the present disclosure describe systems and methods for sharing memory using a multi-ring shared, traversable and dynamic database. In aspects, the database may be synchronized and shared between multiple processes and/or operation mode protection rings of a system. The database may also be persisted to enable the management of information between hardware reboots and application sessions. The information stored in the database may be view independent, traversable, and resizable from various component views of the database. In some aspects, an event processor is additionally described. The event processor may use the database to allocate memory chunks of a shared heap to components/processes in one or more protection modes of the operating system.

Claims (40)

1. A system comprising:

one or more processors; and

memory coupled to at least one of the one or more processors, the memory comprising computer executable instructions that, when executed by the at least one process or, performs a method comprising:

receiving, from a component of the system, a request to make an entry in a dynamic memory database comprising information relating to a shared memory heap, wherein the dynamic memory database is synchronized between two or more processes executing in different operating system modes;

determining, by the dynamic memory database, that the shared memory heap does not comprise enough available memory space to accommodate the requested entry;

requesting, by the dynamic memory database, an allocation of additional memory space for the shared memory heap;

processing, by the shared memory heap, the request for the allocation of additional memory space, the processing including extending the size of the shared memory heap by mapping one or more additional sections of memory to at least one of the two or more processes; and

inserting, by the dynamic memory database, the entry request into the shared memory heap.

2. The system of claim 1 , wherein the dynamic memory database comprises one or more objects of a shared memory heap.

3. The system of claim 1 , wherein the dynamic memory database is persisted to enable management of information between hardware reboots and application sessions.

4. The system of claim 1 , wherein different operating system operation modes comprise at least a kernel mode and a user mode.

5. The system of claim 1 , wherein processing the request for the allocation of additional memory space further comprises copying a current state of the shared memory heap.

6. The system of claim 5 , wherein allocating additional memory space further comprises mapping one or more additional sections of free memory to the shared memory heap to create a modified shared memory heap and copying data in the current state of the shared memory heap to the modified shared memory heap.

7. The system of claim 6 , wherein information mapped to at least one of the two or more processes comprises at least memory addresses from the modified shared memory heap and a pointer object.

8. The system of claim 7 , wherein the pointer object describes a database entry of the dynamic memory database, wherein the database entry corresponds to one or more operations associated with the shared memory heap.

9. The system of claim 1 , wherein the dynamic memory database comprises view independent information.

10. A method comprising:

receiving, from a component of the system, a request to make an entry in a dynamic memory database comprising information relating to a shared memory heap, wherein the dynamic memory database is synchronized between two or more processes executing in different operating system modes;

determining, by the dynamic memory database, that the shared memory heap does not comprise enough available memory space to accommodate the requested entry;

requesting, by the dynamic memory database, an allocation of additional memory space for the shared memory heap;

processing, by the shared memory heap, the request for the allocation of additional memory space, the processing including extending the size of the shared memory heap by mapping one or more additional sections of memory to at least one of the two or more processes; and

inserting, by the dynamic memory database, the entry request into the shared memory heap.

11. The method of claim 10 , wherein the dynamic memory database comprises one or more objects of a shared memory heap.

12. The method of claim 10 , wherein the dynamic memory database is persisted to enable management of information between hardware reboots and application sessions.

13. The method of claim 10 , wherein different operating system operation modes comprise at least a kernel mode and a user mode.

14. The method of claim 10 , wherein processing the request for the allocation of additional memory space further comprises copying a current state of the shared memory heap.

15. The method of claim 10 , wherein the dynamic memory database comprises view independent information.

16. A computer storage media encoding computer executable instructions which, when executed by at least one processor, performs a method for sharing memory using a dynamic memory database, comprising:

submitting a request to a dynamic memory database that is synchronized between two or more processes executing in different operating system operation modes, wherein the dynamic memory database comprises one or more objects of a shared memory heap;

evaluating a shared memory heap associated with the dynamic memory database to determine whether memory space is available to perform the request;

when it is determined that the memory space is not available:

copying a current state of the shared memory heap;

adding additional memory space to the shared memory heap to create a modified shared memory heap; and

inserting the current state of the shared memory heap into the modified shared memory heap;

inserting the request to the dynamic memory database; and

mapping memory information of the modified shared memory heap to at least one of the two or more processes.

17. The computer storage media of claim 16 , wherein the dynamic memory database is persisted to enable the management of information between hardware reboots and application sessions.

18. The computer storage media of claim 16 , wherein the dynamic memory database may be traversed and resized from various component view of the dynamic memory database.

19. The computer storage media of claim 16 , wherein the dynamic memory database comprises a pointer object that references locations in the shared memory heap based on offsets from one or more locations in the shared memory heap.

20. The computer storage media of claim 16 , wherein the dynamic memory database is populated with data from the shared memory heap, and wherein the dynamic memory database is a representation of the shared memory heap.

Assignments (4)
ASSIGNMENT AND ASSUMPTION AGREEMENT Recorded Jul 6, 2023
From: CARBONITE, LLC
To: OPEN TEXT INC.
Reel/Frame 064351/0178 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 29, 2023
From: WEBROOT LLC
To: CARBONITE, LLC
Reel/Frame 064167/0129 →
CERTIFICATE OF CONVERSION Recorded Jun 29, 2023
From: WEBROOT INC.
To: WEBROOT LLC
Reel/Frame 064176/0622 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 2, 2020
From: SHAW, JOHN R., II
To: WEBROOT INC.
Reel/Frame 052308/0889 →
Continuity (3)
Continuation 15888242 · Feb 5, 2018
Provisional Application 62593232 · Nov 30, 2017
Related Publication 20200183835A1 · Jun 11, 2020