Method and apparatus for virtual memory mapping and transaction management in an object-oriented database system

• US 5,426,747 A
• Filed: 03/22/1991
• Issued: 06/20/1995
• Est. Priority Date: 03/22/1991
• Status: Expired due to Term

• Current Assignee: Progress Software Corporation
• Original Assignee: eXcelon Corp. (Progress Software Corporation)
• Inventors: Weinreb, Daniel L., Haradhvala, Sam J.
• Primary Examiner(s): Harvey, Jack B.
• Assistant Examiner(s): LANE, JOHN A
• Application Number:
  US07/674,874
• Time in Patent Office: 1,551 Days
• Field of Search: 395/400, 395/425, 395/600, 364/DIG. 1, 364/DIG. 2
• US Class Current: 711/203
• CPC Class Codes: G06F 12/0813 with a network or matrix configuration
• CPC Class Codes: G06F 12/0815 Cache consistency protocols
• CPC Class Codes: G06F 12/10 Address translation
• CPC Class Codes: G06F 12/1072 Decentralised address translation, e.g. in distributed shared memory systems
• CPC Class Codes: G06F 9/4493 Object persistence
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database

Abstract

An apparatus and method are provided for virtual memory mapping and transaction management in an object-oriented database system having permanent storage for storing data in at least one database, at least one cache memory for temporarily storing data, and a processing unit which runs application programs which request data using virtual addresses. The system performs data transfers in response to memory faults resulting from requested data not being available at specified virtual addressed and performs mapping of data in cache memory. The data in the database may include pointers containing persistent addresses, which pointers are relocated between persistent addresses and virtual addresses. When a data request is made, either for read or write, from a given client computer in a system, other client computers in the system are queried to determine if the requested data is cached and/or locked in a manner inconsistent with the requested use, and the inconsistent caching is downgraded or the transfer delayed until such downgrading can be performed.

Claims

1. An apparatus for virtual memory mapping and transaction management for a database system having at least one permanent storage device for storing at least one database of data including pointers containing persistent addresses, at least one cache memory addressed by physical addresses, and a processing unit including means for requesting data in the at least one cache memory utilizing a virtual address, said apparatus comprising:

means for transferring data between the at least one cache memory and the at least one permanent storage device,

means for relocating inbound persistent addresses in the data requested by the means for requesting into virtual addresses, and

means for mapping virtual addresses of the requested data to physical addresses of the requested data in the at least one cache memory.

2. An apparatus as set forth in claim 1, wherein the database system includes a server computer for each permanent storage device and a client computer for each cache memory and processing unit, wherein each database is divided into segments, each segment containing at least one page, and wherein each segment is divided into a data segment and an information segment.

3. An apparatus as set forth in claim 2, wherein an information segment includes a persistent relocation map which indicates a beginning persistent address for a selected portion of the at least one database and having a given segment and offset, said means for transferring including means for transferring the persistent relocation map, and including means for utilizing the persistent relocation map to determine a persistent address corresponding to a given database, segment and offset.

4. An apparatus as set forth in claim 3, including a virtual address map at each client computer which indicates a beginning virtual address for a selected portion of the at least one database and having a given offset, and means for utilizing the virtual address map to determine a virtual address corresponding to a given database, segment and offset.

5. An apparatus as set forth in claim 4, wherein an application program may involve one or more transactions, the apparatus further comprising:

means, operative when a transaction commits, for relocating outbound all data which was relocated inbound during the transaction;

wherein the means for relocating inbound includes means for utilizing the persistent relocation map to determine a database, segment and offset for a given persistent page address, and means for utilizing the virtual address map to determine a corresponding virtual page address from the determined database, segment and offset; and

wherein the means for relocating outbound includes means for utilizing the virtual address map to determine a database, segment and offset for a given virtual page address, and means for utilizing the persistent relocation map to determine a corresponding persistent page address from the determined database, segment and offset.

6. An apparatus as set forth in claim 5, further comprising means for assigning virtual address space to data, comprising:

means for verifying that the persistent relocation map for the segment containing requested data has been transferred to the client computer,

means for examining each persistent relocation map entry in turn to determine if there is a corresponding virtual address map entry, and

means for creating a new virtual address map entry, and thus assigning virtual address space, for each selected portion of the at least one database for which a virtual address map entry does not exist.

7. A method for virtual memory mapping and transaction management for a database system having at least one permanent storage device for storing at least one database of data including pointers containing persistent addresses, at least one cache memory addressed by physical addresses, and a processing unit including means for requesting data in the at least one cache memory utilizing a virtual address, said method comprising the steps of:

transferring data between the at least one cache memory and the at least one permanent storage device,

relocating inbound persistent addresses in the data requested by the means for requesting into virtual addresses, and

mapping virtual addresses of the requested data to physical addresses of the requested data in the at least one cache memory.

8. A method as set forth in claim 7, wherein the system includes a server computer for each of the at least one permanent storage device and a client computer for each cache memory and processing unit, wherein each database is divided into segments, wherein each segment contains at least one page and is divided into a data segment and an information segment.

9. The method of claim 8, wherein an information segment includes a persistent relocation map which indicates a beginning persistent address for a selected portion of the at least one database and having a given segment and offset, wherein the step of transferring includes transferring the persistent relocation map, and said method further includes a step of determining a persistent address corresponding to a given database, segment and offset utilizing the persistent relocation map.

10. A method as set forth in claim 9 wherein each client computer in the database system has a virtual address map which indicates a beginning virtual address for a selected database portion having a given offset, said method further including a step of determining a virtual address corresponding to a given database, segment and offset utilizing the virtual address map.

11. A method as set forth in claim 10, wherein the database system includes an application program which performs at least one transaction, said method further comprising the steps of:

relocating outbound, when a transaction commits, all data which was relocated inbound during the transaction,

wherein the step of relocating inbound includes the steps of utilizing the persistent relocation map to determine a database, segment and offset for a given persistent page address and utilizing the virtual address map to determine a corresponding virtual page address from the determined database, segment and offset, and

wherein the step of relocating outbound includes the steps of utilizing the virtual address map to determine a database, segment and offset for a given virtual page address, and utilizing the persistent relocation map to determine a corresponding persistent page address from the determined database, segment and offset.

12. A method as set forth in claim 11, further comprises a step of assigning virtual address space including the steps of:

verifying that the persistent relocation map for the segment containing the requested data has been transferred to the client computer,

determining whether there is a corresponding virtual address map entry for each persistent relocation map entry for all selected database portions having a persistent relocation map entry, and

creating a new virtual address map entry for each selected portion of at least one database for which it is determined that a virtual address map entry does not exist.