# US 2013/0159452 A1 · Memory Server Architecture

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0159452 A1
- Document ID: US20130159452A1
- Status: Published application
- Kind: A1
- Application number: 13/693,033
- Filed: 2012-12-03
- Published: 2013-06-20
- Earliest claimed: 2011-12-06
- Inventors: Manuel Alejandro Saldana De Fuentes; Paul Chow
- Web page: https://patentgrep.com/patent/US20130159452A1

## CPC

- G06F 15/167: using a common memory, e.g. mailbox
- G06F 15/7867: {with reconfigurable architecture}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A memory server system is provided herein. It includes a first plurality of Field Programmable Gate Arrays (FPGA) application server nodes that are configured to parse the location of the FPGA data server nodes; a second plurality of FPGA data server nodes that are configured as memory controllers, each of the second plurality of FPGA data server nodes being connected to a plurality of RAM memory banks; and a network connection between the first plurality of FPGAs and the second plurality of FPGA processing nodes.

## Claims

### Claim 1

A memory server architecture comprising:
A plurality of Application Server nodes executing software applications in an Internet-accessible environment;
wherein the plurality of Application Servers are programmed to access data from a plurality of Data Servers;
wherein the plurality of Data Servers respond to data requests from the plurality of Application Servers;
wherein the plurality of Data Servers comprises a first plurality of back-end FPGAs structured to provide access to a plurality of RAM;
wherein the first plurality of back-end FPGAs are configured to process data requests in the form of key-value or address-value pairs.

### Claim 2 (depends on 1)

The memory server architecture of claim 1, wherein
the key in a key-value format is hashed by the back-end FPGAs to determine the Local Address on a Data Server;
and the Global Address in an address-value format is used directly by the back-end FPGAs or mapped by the back-end FPGAs to a Local Address on a Data Server.

### Claim 3 (depends on 1)

The memory server architecture of claim 1, wherein
the first plurality of back-end FPGAs can perform in-line processing on the data to be stored and retrieved from the plurality of RAM on a Data Server;
wherein the in-line processing operations performed on the data includes, but is not limited to protocol parsing, key hashing, compression, encryption and other TCP/IP- or UDP-related functions, such as checksum calculations.

### Claim 4 (depends on 1)

The memory server architecture of claim 1, wherein
the first plurality of back-end FPGAs are programmed to include hardware agents that provide data-caching services including, but not limited to data cache eviction, memory management, cache searching, response generation, command parsing, and protocol parsing;
wherein the protocol parsing includes supporting Memcached and other similar key-value data caching libraries;
wherein the data-caching service can respond to multiple requests simultaneously.

### Claim 5 (depends on 1)

The memory server architecture of claim 1, wherein
the first plurality of back-end FPGAs are programmed to process data requests providing:
a LAN interface to communicate with a LAN;
a LAN-to-NoC bridge operatively connected to the LAN interface and the NoC;
wherein the LAN-to-NoC bridge performs LAN port mapping to NoC addresses;
the NoC being operatively accessed by off-chip communication controllers;
the NoC being operatively connected to a plurality of hardware memory agents;
each hardware memory agent being connected to a plurality of memory controllers;
each memory controller being implemented entirely in the back-end FPGA, but some aspects may be implemented externally;
each memory controller is structurally connected to a plurality of RAM.

### Claim 6 (depends on 1)

The memory server architecture of claim 1, wherein
the plurality of back-end FPGAs are on a multiple FPGA board providing;
multiple network connections accessible by the FPGAs;
a host interface accessible by the FPGAs;
a plurality of RAM accessible by the FPGAs;
wherein the FPGAs are structurally grouped into clusters;
wherein each FPGA in a cluster may be connected to other FPGAs in the cluster using intra-cluster communication links;
wherein each cluster may be connected to other clusters on the board using inter-cluster communication links.

### Claim 7

A memory server architecture comprising:
A plurality of Application Server nodes executing software applications in an Internet-accessible environment;
wherein the plurality of Application Servers are programmed to access data from a plurality of Data Servers;
wherein the plurality of Data Servers respond to data requests from the plurality of Application Servers;
wherein the plurality of Data Servers comprises a first plurality of back-end FPGAs structured to provide access to a plurality of RAM;
wherein the first plurality of back-end FPGAs are configured to process data requests in the form of key-value or address-value pairs;
wherein a second plurality of front-end FPGAs are configured to issue data requests in the form of key-value or address-value pairs.

### Claim 8 (depends on 7)

The memory server architecture of claim 7, wherein
the key in a key-value format is hashed by the back-end FPGAs to determine the Local Address on a Data Server;
and the Global Address in an address-value format is used directly by the back-end FPGAs or mapped by the back-end FPGAs to a Local Address on a Data Server.

### Claim 9 (depends on 7)

The memory server architecture of claim 7, wherein
the first plurality of back-end FPGAs can perform in-line processing on the data to be stored and retrieved from the plurality of RAM on a Data Server;
wherein the in-line processing operations performed on the data includes, but is not limited to protocol parsing, key hashing, compression, encryption and other TCP/IP- or UDP-related functions, such as checksum calculations.

### Claim 10 (depends on 7)

The memory server architecture of claim 7, wherein
the first plurality of back-end FPGAs are programmed to include hardware agents that provide data-caching services including, but not limited to data cache eviction, memory management, cache searching, response generation, command parsing, and protocol parsing;
wherein the protocol parsing includes supporting Memcached and other similar key-value data caching libraries;
wherein the data-caching service can respond to multiple requests simultaneously.

### Claim 11 (depends on 7)

The memory server architecture of claim 7, wherein
the first plurality of back-end FPGAs are programmed to process data requests by providing:
a LAN interface to communicate with a LAN;
a LAN-to-NoC bridge operatively connected to the LAN interface and the NoC;
wherein the LAN-to-NoC bridge performs LAN port mapping to NoC addresses;
the NoC being operatively accessed by off-chip communication controllers;
the NoC being operatively connected to a plurality of hardware memory agents;
each hardware memory agent being connected to a plurality of memory controllers;
each memory controller being implemented entirely in the back-end FPGA, but some aspects may be implemented externally;
each memory controller is structurally connected to a plurality of RAM.

### Claim 12 (depends on 7)

The memory server architecture of claim 7, wherein
the plurality of back-end FPGAs are on a multiple FPGA board providing;
multiple network connections accessible by the FPGAs;
a host interface accessible by the FPGAs;
a plurality of RAM accessible by the FPGAs;
wherein the FPGAs are structurally grouped into clusters;
wherein each FPGA in a cluster may be connected to other FPGAs in the cluster using intra-cluster communication links;
wherein each cluster may be connected to other clusters on the board using inter-cluster communication links.

### Claim 13 (depends on 7)

The memory server architecture of claim 7, wherein
the first plurality of front-end FPGAs are programmed to issue data requests by providing:
a host interface structured to communicate with a hardware proxy module;
wherein the hardware proxy module interprets commands from an application running on an Application Server;
wherein the hardware proxy module provides efficient memory access, such as DMA, to and from the Application Server main memory;
wherein the hardware proxy may be structured to communicate with a hash engine;
wherein the hash engine is used in a key-value system to perform key hashing to determine the Data Server to access;
wherein the hash engine is used in an address-value system to map Global Addresses to determine the Data Server to access;
wherein the hash engine is structured to communicate with optional in-line pre-processing capabilities for data before it is sent for storage and after it is retrieved from storage.

### Claim 14 (depends on 7)

The memory server architecture of claim 7, wherein
the first plurality of front-end FPGAs are programmed to include hardware agents that provide data-caching services including, but not limited to data cache eviction, memory management, cache searching, response generation, command parsing, and protocol parsing;
wherein the protocol parsing includes supporting Memcached and other similar key-value data caching libraries;
wherein the data-caching service can respond to multiple requests simultaneously.

### Claim 15 (depends on 7)

The memory server architecture of claim 7, wherein the plurality of front-end FPGAs are on a multiple FPGA board providing;
multiple network connections accessible by the FPGAs;
a host interface accessible by the FPGAs;
a plurality of RAM accessible by the FPGAs;
wherein the FPGAs are structurally grouped into clusters;
wherein each FPGA in a cluster may be connected to other FPGAs in the cluster using intra-cluster communication links;
wherein each cluster may be connected to other clusters on the board using inter-cluster communication links.

### Claim 16 (depends on 7)

The memory server architecture of claim 7, wherein
a plurality of software libraries are provided;
wherein each software library provides a high-level interface that simplifies the complexities of controlling the front-end FPGA and exchanging data with the front-end FPGA;
the API being available in a plurality of computer programming languages.

### Claim 17 (depends on 7)

The memory server architecture of claim 7, wherein
two networks are used to separate the traffic between the Application Servers and the database servers, and the traffic between the Application Servers and the Data Servers;
wherein the first network is the existing LAN infrastructure connecting the Application Servers to the database servers;
wherein the second network is structured to provide connections between the front-end FPGAs to the back-end FPGAs using point-to-point links;
wherein the front-end and back-end FPGAs both perform network packet routing.
