G06F12/0891

MEMORY CONTROLLER ZERO CACHE
20230236985 · 2023-07-27 ·

In one embodiment, a controller in a microprocessor, the controller configured to manage accesses to dynamic random access memory (DRAM), the controller comprising: a first table configured to track cache lines that have been written to zero for a plurality of first memory regions; and a second table configured to track the cache lines that have been written to zero for a plurality of second memory regions, wherein each of the plurality of second memory regions comprises a group of the plurality of first memory regions where all of the cache lines within each of the plurality of the first memory regions within the group have been written to zero.

MEMORY CONTROLLER ZERO CACHE
20230236985 · 2023-07-27 ·

In one embodiment, a controller in a microprocessor, the controller configured to manage accesses to dynamic random access memory (DRAM), the controller comprising: a first table configured to track cache lines that have been written to zero for a plurality of first memory regions; and a second table configured to track the cache lines that have been written to zero for a plurality of second memory regions, wherein each of the plurality of second memory regions comprises a group of the plurality of first memory regions where all of the cache lines within each of the plurality of the first memory regions within the group have been written to zero.

SELECTABLE CACHE POLICY
20230236977 · 2023-07-27 ·

Apparatuses, systems, and techniques to select cache policies. In at least one embodiment, a system causes one or more cache policies of one or more caches to be selected based, at least in part, on one or more neural networks to use data stored in the one or more caches.

SELECTABLE CACHE POLICY
20230236977 · 2023-07-27 ·

Apparatuses, systems, and techniques to select cache policies. In at least one embodiment, a system causes one or more cache policies of one or more caches to be selected based, at least in part, on one or more neural networks to use data stored in the one or more caches.

Consistent client-side caching for fine grained invalidations

An approach for implementing function semantic based partition-wise SQL execution and partition pruning in a data processing system is provided. The system receives a query directed to a range-partitioned table and determines if operation key(s) of the query include function(s) over the table partitioning key(s). If so, the system obtains a set of values corresponding to each partition by evaluating the function(s) on a low bound and/or a high bound table partitioning key value corresponding to the partition. The system may then compare the sets of values corresponding to different partitions and determine whether to aggregate results obtained by executing the query over the partitions based on the comparison. The system may also determine whether to prune any partitions from processing based on a set of correlations between the set of values for each partition and predicate(s) of the query including function(s) over the table partitioning key(s).

Consistent client-side caching for fine grained invalidations

An approach for implementing function semantic based partition-wise SQL execution and partition pruning in a data processing system is provided. The system receives a query directed to a range-partitioned table and determines if operation key(s) of the query include function(s) over the table partitioning key(s). If so, the system obtains a set of values corresponding to each partition by evaluating the function(s) on a low bound and/or a high bound table partitioning key value corresponding to the partition. The system may then compare the sets of values corresponding to different partitions and determine whether to aggregate results obtained by executing the query over the partitions based on the comparison. The system may also determine whether to prune any partitions from processing based on a set of correlations between the set of values for each partition and predicate(s) of the query including function(s) over the table partitioning key(s).

STORAGE CONTROLLER DEALLOCATING MEMORY BLOCK, METHOD OF OPERATING THE SAME, AND METHOD OF OPERATING STORAGE DEVICE INCLUDING THE SAME

Disclosed is a method of operating a storage controller, the storage controller communicating with a host and a non-volatile memory device. The method includes receiving a first erase request from the host, the first erase request being for a first zone of a plurality of zones of the non-volatile memory device, loading first allocation list information of the first zone from an allocation list table based on the first erase request, deallocating memory blocks allocated to the first zone based on the first allocation list information, wherein sequential physical page numbers of the memory blocks are respectively mapped onto sequential logical page numbers, and providing the non-volatile memory device with a physical erase request for the deallocated memory blocks of the first zone.

STORAGE CONTROLLER DEALLOCATING MEMORY BLOCK, METHOD OF OPERATING THE SAME, AND METHOD OF OPERATING STORAGE DEVICE INCLUDING THE SAME

Disclosed is a method of operating a storage controller, the storage controller communicating with a host and a non-volatile memory device. The method includes receiving a first erase request from the host, the first erase request being for a first zone of a plurality of zones of the non-volatile memory device, loading first allocation list information of the first zone from an allocation list table based on the first erase request, deallocating memory blocks allocated to the first zone based on the first allocation list information, wherein sequential physical page numbers of the memory blocks are respectively mapped onto sequential logical page numbers, and providing the non-volatile memory device with a physical erase request for the deallocated memory blocks of the first zone.

Extended cache for efficient object store access by a database

Disclosed herein are system, method, and computer program product embodiments for utilizing an extended cache to access an object store efficiently. An embodiment operates by executing a database transaction, thereby causing pages to be written from a buffer cache to an extended cache and to an object store. The embodiment determines a transaction type of the database transaction. The transaction type can a read-only transaction or an update transaction. The embodiment determines a phase of the database transaction based on the determined transaction type. The phase can be an execution phase or a commit phase. The embodiment then applies a caching policy to the extended cache for the evicted pages based on the determined transaction type of the database transaction and the determined phase of the database transaction.

Extended cache for efficient object store access by a database

Disclosed herein are system, method, and computer program product embodiments for utilizing an extended cache to access an object store efficiently. An embodiment operates by executing a database transaction, thereby causing pages to be written from a buffer cache to an extended cache and to an object store. The embodiment determines a transaction type of the database transaction. The transaction type can a read-only transaction or an update transaction. The embodiment determines a phase of the database transaction based on the determined transaction type. The phase can be an execution phase or a commit phase. The embodiment then applies a caching policy to the extended cache for the evicted pages based on the determined transaction type of the database transaction and the determined phase of the database transaction.