Hierarchical immutable content-addressable memory processor
First Claim
Patent Images
1. A computer system comprising:
- a content-addressable physical memory including a plurality of physical memory blocks, wherein when one of said memory blocks is created by setting it to an active state, its contents are considered immutable; and
a memory controller, wherein data to be written to said physical memory is compared to contents of a set of said memory blocks that are indicated as being in an active state at the time of writing to avoid writing data to a memory block considered immutable.
2 Assignments
0 Petitions
Accused Products
Abstract
Improved memory management is provided according to a Hierarchical Immutable Content Addressable Memory Processor (HICAMP) architecture. In HICAMP, physical memory is organized as two or more physical memory blocks, each physical memory block having a fixed storage capacity. An indication of which of the physical memory blocks is active at any point in time is provided. A memory controller provides a non-duplicating write capability, where data to be written to the physical memory is compared to contents of all active physical memory blocks at the time of writing, to ensure that no two active memory blocks have the same data after completion of the non-duplicating write.
-
Citations
20 Claims
-
1. A computer system comprising:
-
a content-addressable physical memory including a plurality of physical memory blocks, wherein when one of said memory blocks is created by setting it to an active state, its contents are considered immutable; and a memory controller, wherein data to be written to said physical memory is compared to contents of a set of said memory blocks that are indicated as being in an active state at the time of writing to avoid writing data to a memory block considered immutable. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A method of computer system memory management comprising:
-
in a content-addressable physical memory including a plurality of physical memory blocks, creating one of said memory blocks by setting it to an active state so that its contents are considered immutable; and using a memory controller to compare contents of a set of said memory blocks that are indicated as being in an active state at the time of writing to avoid writing data to a memory block considered immutable. - View Dependent Claims (8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20)
-
Specification