# low-latency-ethernet

**Repository Path**: aliveda/low-latency-ethernet

## Basic Information

- **Project Name**: low-latency-ethernet
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: MIT
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2024-11-16
- **Last Updated**: 2024-11-16

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# Low latency verilog ethernet for Nasdaq HFT FPGA

RTL implementation of a low latency ethernet interface for the purposes of the HFT FPGA project.

In order to help acheive a lower latency all features not stricktly necessary for our
use case will be stripped out. External users should assume this project will be re-usable 
for a different use case or that it is compliant with 802.3.

### PHY 

IP for both 10GBASE-R and 4 lane 40GBASE-R, see submodule.

### MAC

Features :

- Support VLAN tagging, does not support double VLAN tagging

Assumptions :

- Full duplex interface only 


### UDP 

#### rx data stream

Features : 

- IPv4, no support for framgmentation

- Support options, discard there data

- only supports UDP, ignors all other packet types

Assumptions : 

- UDP packets containing MoldUDP64 datagrams will never be framgmented

#### tx retransmission request

Features : 

- IPv4

- all data will be packaged into an UDP packet

- all packets will be destined to the same destination

- No backpressure will be applied on UDP data provider

Assumptions : 

- UDP data provider will potencially transmit data with bubbles, valid signal will be provided

### TCP

RTL implementation of a single socket `TCP` module.

Features : 

- IPv4

Assumptions : 

- ITCH server is located at a single designation address

- There will only be 1 connection alive at a time

### Common features and assumptions

Features and assumptions shared amoung all ethernet interface.

Features :

- IP is staticly defined 

- Gateway MAC is statically defined

Assumptions :

- Remote server address will never change 

- I can send an ack faster than I can receive new packets

- No packet segmentation
 

### Roadmap 

Under developpement : 

- [x] PCS 10G 16b wide data path

- [x] PCS 40G 256b wide data path

- [x] MAC 10G 16b/32b/64b wide data path

- [x] IPv4 16b

- [ ] IPv4 64b

- [x] UDP 16b

- [ ] UDP

- [x] TCP 16b