# Xenic: SmartNIC-accelerated distributed transacitions

### Presentation 

* Distributed transactions in the datacenter 
  * Our target: distributed ACID transactions are a replicated, in-memory database
  * Common approach: optimistic concurrency control + replication 
  * Viability depends on efficient remote operations --> hardware acceleration
*   Recent work applies RDMA 
  * One-sided read/write primitives are high-performance, but restrict design 
    * Impact data structure and protocol overheads 
    * ![](https://2097630930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MVORxAomcgtzVVUqmws%2Fuploads%2F0GZlzafhaXhcIQoUfbXJ%2Fimage.png?alt=media\&token=cb162401-8e83-4a25-846f-cc68170aca48)
    * ![](https://2097630930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MVORxAomcgtzVVUqmws%2Fuploads%2FmpFS3BmsZGvYp2b6LR0j%2Fimage.png?alt=media\&token=c30a050d-370f-4fe1-a8e0-f17a83d64a68)
  * Two-sided RPCs are costly 
    * Add latency overhead, processing costs 
  * FaRM: one-sided RDMA
  * FaSST: two-sided RPCs 
  * DrTM+H: uses both  
  * Ongoing debate of applying RDMA: trade-offs are necessary 
* On-path SmartNICs: another option for hardware acceleration 
  * Programmable remote operations, without host processing 
  * Cost-effective compute: \~30% of NIC die area, 25W line-rate processing 
* SmartNIC opportunities 
  * Flexible CPU-bypass remote operations
  * Latency savings via stateful NIC operations, efficient PCIe DMA 
  * Efficient NIC-to-NIC communication 
  * But 
    * Software packet pipeline --> latency overhead 
    * Limited NIC resources 
* Xenic 
  * Distributed transactions accelerated with on-path SmartNICs 
  * Key
    * Co-designed data store, spread across NIC + host DRAM 
      * Minimize lookup overhead, utilizing NIC's on-board memory 
    * SmartNIC function shipping
      * Offload transaction logic to avoid PCIe crossings 
    * Multi-hop OCC protocols 
      * Reduce communication with optimized message patterns
    *  Stateful, asynchronous SmartNIC operation framework 
      * Exploit the SmartNIC's hardware interfaces 
* Xenic: Robinhood Data Store 
  * Host DRAM contains all objects; SmartNIC caches objects and lookup hints
  * Critical path accesses: NIC memory hit or DMA read, DMA log write 
    * Lookup hints limit DMA cost for cache misses 
      * Cache miss: bounded DMA R
      * Cache hit: NIC DRAM 
    * OCC + pinning ensure NIC/host consistency 
    * ![](https://2097630930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MVORxAomcgtzVVUqmws%2Fuploads%2FHtFx4IrK20TT1s6aZ4sJ%2Fimage.png?alt=media\&token=078fb346-014a-4f32-9e52-2de76bcc566c)
* Xenic: SmartNIC function shipping 
  * Provides SmartNIC cores as a function shipping target 
  * Shipping execution can reduce overhead, depending on application-level computation and state requirements 
  * Saves coordinator PCIe crossings 
* Xenic: multi-hop OCC protocols 
  * Ships execution to remote SmartNICs
  * Multi-hop NIC-to-NIC communication increases network efficiency 
    * ![](https://2097630930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MVORxAomcgtzVVUqmws%2Fuploads%2FJlWw1KqU8uf6qWtcASLm%2Fimage.png?alt=media\&token=39d1005f-5133-4aba-bb26-da01dc1a812c)
* Evaluation 
  * Robinhood + NIC lookup hints effectively reduce cost
  * SmartNIC increases DMA lookup efficiency, even for cache misses
  * For FaRM and DrTM+H, end-to-end bandwidth/latency cost 
  * Better latency & throughput than RPC, RDMA, hybrid designs 
  * Also measured in our paper 
    * Cumulative core savings 
    * Full TPC-C, Retwis, Smallbank 
* Summary: high-performance, CPU-efficient distributed transactions 
  * Leveraging on-path SmartNICs:
    * Avoids RDMA compromises 
    * Provides a new, remote access-optimized data store
    * Selectively offloads transaction logic 
    * Applies multi-hop communication patterns 
    * Delivers >2x throughput over 100Gbps RDMA, latency savings relative to RPCs 


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://sliu583.gitbook.io/blog/conference/index/sosp-21/smartnic/xenic-smartnic-accelerated-distributed-transacitions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.