Intel Corporation

Chet R Douglas

Nathan Marushak

Wei P Chen

Rajat Agarwal

Andy M Rudoff

Tiffany J Kasanicky

Ashok Raj

Narayan Ranganathan

Sivakumar Radhakrishnan

Brian J Skerry

Francis Corrado

Dan J Williams

Vishal Verma

A memory management system includes a cache invalidation logic configured to invalidate, based a cache invalidation event, cache entries within a cache memory by having each cache entry, of the cache entries within the cache memory, reference a respective dummy address from among dummy addresses within a dummy address space, wherein the cache memory is assigned to a memory, the memory has a memory address space associated therewith to provide access the memory, and each dummy address of the dummy addresses within the dummy address space is distinct from any address of the memory address space.

Memory system, computing system, and methods thereof for cache invalidation with dummy address space

According to various aspects, a memory system may include: a memory having a memory address space associated therewith to access the memory; a cache memory assigned to the memory; one or more processors configured to generate a dummy address space in addition to the memory address space, each address of the dummy address space being distinct from any address of the memory address space, and generate one or more invalid cache entries in the cache memory, the one or more invalid cache entries referencing one or more dummy addresses of the dummy address space.

In one embodiment, a block data transfer interface employing offload data transfer engine in accordance with the present description includes an offload data transfer engine executing a data transfer command set to transfer a block of data in a transfer data path from a source memory to a new region of a destination memory, wherein the transfer data path bypasses a central processing unit to minimize or reduce involvement of the central processing unit in the block transfer. In response to a successful transfer indication, a logical address is re-mapped to a physical address of the new region of the destination memory, instead of a physical address of the original region of the destination memory. In one embodiment, the re-mapping is performed by a central processing unit. In another embodiment, the re-mapping is performed by the offload data transfer engine. Other aspects are described herein.

Offload data transfer engine for a block data transfer interface

A method according to one embodiment may include communicating, by an integrated circuit, with at least one target ATA/ATAPI storage device. The method of this embodiment may also include creating, by the integrated circuit, a persistent reservation between at least one target ATA/ATAPI storage device and the integrated circuit. Of course, many alternatives, variations, and modifications are possible without departing from this embodiment.

Integrated circuit capable of persistent reservations

In one embodiment, a method is provided that may include generating, at least in part by first circuitry comprised in an integrated circuit, check data based at least in part upon other data, and/or determining at least in part by the first circuitry, one or more locations of the check data and/or the other data in storage. The first circuitry may be capable of regenerating the other data based at least in part upon the check data. The method also may include issuing a request from second circuitry also comprised in the integrated circuit requesting that a wireless communication device transmit the other data, and/or receiving, by the second circuitry, a request issued from the wireless device, to retrieve the other data. Of course, many alternatives, variations, and modifications are possible without departing from this embodiment.

Integrated circuit using wireless communication to store and/or retrieve data and/or check data

A method according to one embodiment may include communicating, by an expander device, with at least one initiator engine using at least a first communication protocol and at least one target storage device using at least a second communication protocol. The method of this embodiment may also include translating, by the expander device, between first commands transmitted using the first communication protocol and second commands transmitted using the second communication protocol. Of course, many alternatives, variations, and modifications are possible without departing from this embodiment.

Expander device capable of communication protocol translation

In one embodiment, a method is provided that may include generating, at least in part, an identifier to be associated with a group of devices. The group of devices may comprise at least two devices. The identifier may be generated, at least in part, based, at least in part, upon respective source identifiers identifying, at least in part, respective sources of the at least two devices. Of course, many modifications, variations, and alternatives are possible without departing from this embodiment.

Mechanism for generating a virtual identifier

A method according to one embodiment may include creating at least one of a persistent reservation and a persistent affiliation between one or more target SATA storage devices and one or more initiator engines. Of course, many alternatives, variations, and modifications are possible without departing from this embodiment.

Expander device capable of persistent reservations and persistent affiliations

Provided are a method, system, and program for managing requests to an Input/Output (I/O) device. The I/O requests directed to the I/O device are queued and a determination is made as to whether a number of queued I/O requests exceeds a threshold. If the number of queued I/O requests exceeds the threshold, then a coalesce limit is calculated. A number of queued I/O requests not exceeding the calculated coalesce limit are coalesced into a coalesced /O request and the coalesced I/O request is transmitted.

Growing community of inventors

Tucson, AZ, United States of America

Chet R Douglas