# US 2019/0245911 A1 · Address space management with respect to a coherent accelerator processor interface architecture

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

- Number: US 2019/0245911 A1
- Document ID: US20190245911A1
- Status: Published application
- Kind: A1
- Application number: 16/391,463
- Filed: 2019-04-23
- Published: 2019-08-08
- Earliest claimed: 2017-01-08
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Shajith Chandran; Vishal Ramachandra Mansur
- Web page: https://patentgrep.com/patent/US20190245911A1

## CPC

- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- H04L 43/20: the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
- G06F 3/0611: {in relation to response time}
- G06F 9/45508: {Runtime interpretation or emulation, e g. emulator loops, bytecode interpretation}
- G06F 9/45533: {Hypervisors; Virtual machine monitors}
- G06F 12/1009: using page tables, e.g. page table structures
- G06F 12/109: for multiple virtual address spaces, e.g. segmentation (G06F12/1036 takes precedence)
- G06F 13/1668: {Details of memory controller}
- G06F 15/7871: {Reconfiguration support, e.g. configuration loading, configuration switching, or hardware OS}
- H04L 43/0852: Delays
- H04L 43/0876: Network utilisation, e.g. volume of load or congestion level
- H04L 67/025: for remote control or remote monitoring of applications
- H04L 69/329: in the application layer [OSI layer 7]
- G06F 13/4282: {on a serial bus, e.g. I2C bus, SPI bus (on daisy chain buses G06F13/4247)}
- G06F 2009/45583: {Memory management, e.g. access or allocation}
- G06F 2212/151: Emulated environment, e.g. virtual machine
- H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04L 41/5003: Managing SLA; Interaction between SLA and QoS
- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Disclosed aspects relate to address space management with respect to a Coherent Accelerator Processor Interface (CAPI) architecture. A shared CAPI component may be established to access a plurality of address spaces of a plurality of assets. The plurality of assets may include both a first asset which corresponds to a first address space of the plurality of address spaces and a second asset which corresponds to a second address space of the plurality of address spaces. A request may be detected to process a set of data and route a set of processed data from the first asset to the second asset. The set of data may be processed to form the set of processed data. The set of processed data may be routed from the first address space to the second address space to fulfill the request.

## Claims

### Claim 1

A method for processing data in an accelerator pipeline, the accelerator pipeline including a plurality of accelerator nodes, each accelerator node being a field-programmable gate array (FPGA) programmed with a separate Coherence Accelerator Processor Interface (CAPI) architecture, each CAPI architecture comprising a plurality of address spaces shared among the corresponding FPGA and a plurality of corresponding threads to create a shared CAPI context, the method comprising:
storing, by a first thread of a first plurality of threads and within a first shared CAPI context, data to be processed in a first address space of a first plurality of address spaces shared among a first FPGA of a first accelerator node of the accelerator pipeline and the first plurality of threads such that the data is directly accessible by the first plurality of threads and the first FPGA;
obtaining, by the first FPGA, the data from the first address space;
processing, by the first FPGA, the data;
storing, by the first FPGA, the processed data in a second address space of the first plurality of address spaces such that the processed data is directly accessible by the first plurality of threads and the first FPGA; and
transferring the processed data from the first accelerator node to a second accelerator node of the accelerator pipeline whereby the transferred data becomes directly accessible, within a second shared CAPI context, to a second FPGA of the second accelerator node and a second plurality of threads sharing a second plurality of address spaces among each other and the second FPGA.
