> For the complete documentation index, see [llms.txt](https://dma.lystic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dma.lystic.dev/fpga-devices/limitations.md).

# Limitations

## Read/Write Speed Limitations

DMA devices can come in a wide range of speeds. For DMA cheating, we need high speed, low latency, and very good stability. Sadly, most cards on the market don't provide us with all three of these factors. 

You can expect about 1000 r/w TLPs per second. This is a really tight restriction for cheating, so we need to be smart about our read operations. If we can read 4096 bytes in one read operation, and from that get multiple pointers or values, that is more efficient than reading each value or pointer on its own. 

{% hint style="info" %}
Ulf Frisk discusses latency and speed on [this](https://github.com/ufrisk/pcileech/issues/56) git issue.
{% endhint %}

### See also:

{% content-ref url="/pages/-MfS3ZdYn0dkSFbuXUJj" %}
[Broken mention](broken://pages/-MfS3ZdYn0dkSFbuXUJj)
{% endcontent-ref %}

## IOMMU Limitation

The [IOMMU ](https://en.wikipedia.org/wiki/Input%E2%80%93output_memory_management_unit)is a middle man between our DMA device and the physical memory. In order for our DMA cards to work, this feature needs to be turned off. 

{% hint style="info" %}
Anticheats do not require IOMMU to be enabled yet.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://dma.lystic.dev/fpga-devices/limitations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.