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/documentation/articlesvm-design_index/en/?format=api",
    "source": [
        "FreeBSD makes use of several page queues to further refine the selection of pages to reuse as well as to determine when dirty pages must be flushed to their backing store.  Since page tables are dynamic entities under FreeBSD, it costs virtually nothing to unmap a page from the address space of any processes using it.  When a page candidate has been chosen based on the page-use counter, this is precisely what is done.  The system must make a distinction between clean pages which can theoretically be freed up at any time, and dirty pages which must first be written to their backing store before being reusable.  When a page candidate has been found it is moved to the inactive queue if it is dirty, or the cache queue if it is clean.  A separate algorithm based on the dirty-to-clean page ratio determines when dirty pages in the inactive queue must be flushed to disk.  Once this is accomplished, the flushed pages are moved from the inactive queue to the cache queue.  At this point, pages in the cache queue can still be reactivated by a VM fault at relatively low cost.  However, pages in the cache queue are considered to be \"immediately freeable\" and will be reused in an LRU (least-recently used) fashion when the system needs to allocate new memory."
    ],
    "previous_source": "",
    "target": [
        "FreeBSD makes use of several page queues to further refine the selection of pages to reuse as well as to determine when dirty pages must be flushed to their backing store.  Since page tables are dynamic entities under FreeBSD, it costs virtually nothing to unmap a page from the address space of any processes using it.  When a page candidate has been chosen based on the page-use counter, this is precisely what is done.  The system must make a distinction between clean pages which can theoretically be freed up at any time, and dirty pages which must first be written to their backing store before being reusable.  When a page candidate has been found it is moved to the inactive queue if it is dirty, or the cache queue if it is clean.  A separate algorithm based on the dirty-to-clean page ratio determines when dirty pages in the inactive queue must be flushed to disk.  Once this is accomplished, the flushed pages are moved from the inactive queue to the cache queue.  At this point, pages in the cache queue can still be reactivated by a VM fault at relatively low cost.  However, pages in the cache queue are considered to be \"immediately freeable\" and will be reused in an LRU (least-recently used) fashion when the system needs to allocate new memory."
    ],
    "id_hash": 2673623526903959567,
    "content_hash": 2673623526903959567,
    "location": "documentation/content/en/articles/vm-design/_index.adoc:239",
    "context": "",
    "note": "type: Plain text",
    "flags": "",
    "labels": [],
    "state": 100,
    "fuzzy": false,
    "translated": true,
    "approved": false,
    "position": 51,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": false,
    "num_words": 222,
    "source_unit": "https://translate-dev.freebsd.org/api/units/615411/?format=api",
    "priority": 100,
    "id": 615411,
    "web_url": "https://translate-dev.freebsd.org/translate/documentation/articlesvm-design_index/en/?checksum=a51a9e6ea83cd00f",
    "url": "https://translate-dev.freebsd.org/api/units/615411/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2021-03-20T20:43:34.977307Z"
}