Unit Instance

HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "translation": "https://translate-dev.freebsd.org/api/translations/freebsd-doc/boooks_arch-handbook/pt_BR/?format=api",
    "source": [
        "Before calling the callback function from <function>bus_dmamap_load()</function> the segment array is stored in the stack. And it gets pre-allocated for the maximal number of segments allowed by the tag. As a result of this the practical limit for the number of segments on i386 architecture is about 250-300 (the kernel stack is 4KB minus the size of the user structure, size of a segment array entry is 8 bytes, and some space must be left). Since the array is allocated based on the maximal number this value must not be set higher than really needed. Fortunately, for most of hardware the maximal supported number of segments is much lower. But if the driver wants to handle buffers with a very large number of scatter-gather segments it should do that in portions: load part of the buffer, transfer it to the device, load next part of the buffer, and so on."
    ],
    "previous_source": "",
    "target": [
        "Antes de chamar a fun��o de retorno de chamada <function> bus_dmamap_load () </function> o array de segmentos � armazenado na pilha. E ele � pr�-alocado para o n�mero m�ximo de segmentos permitido pela tag. Devido a isso, o limite pr�tico para o n�mero de segmentos na arquitetura i386 � de cerca de 250-300 (a pilha do kernel � 4KB menos o tamanho da estrutura do usu�rio, o tamanho de uma entrada de matriz de segmento � de 8 bytes e algum espa�o deve ser deixado) . Como a matriz � alocada com base no n�mero m�ximo, esse valor n�o deve ser definido mais alto do que o realmente necess�rio. Felizmente, para a maioria do hardware, o n�mero m�ximo de segmentos suportados � muito menor. Mas se o driver quiser manipular buffers com um n�mero muito grande de segmentos de dispers�o, ele deve fazer isso em partes: carregar parte do buffer, transferi-lo para o dispositivo, carregar a pr�xima parte do buffer e assim por diante. "
    ],
    "id_hash": 5944484303631366233,
    "content_hash": 5944484303631366233,
    "location": "book.translate.xml:17809",
    "context": "",
    "note": "(itstool) path: sect1/para",
    "flags": "",
    "labels": [],
    "state": 10,
    "fuzzy": true,
    "translated": false,
    "approved": false,
    "position": 1935,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": true,
    "num_words": 150,
    "source_unit": "https://translate-dev.freebsd.org/api/units/229393/?format=api",
    "priority": 100,
    "id": 229441,
    "web_url": "https://translate-dev.freebsd.org/translate/freebsd-doc/boooks_arch-handbook/pt_BR/?checksum=d27f0cfa9ad53859",
    "url": "https://translate-dev.freebsd.org/api/units/229441/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2021-01-09T14:37:34.042826Z"
}