Translation status

93 Strings 89%
Browse Translate
6,345 Words 88%

Strings status

93
All strings — 6,345 words Browse Translate Zen
83
Translated strings — 5,609 words Browse Translate Zen
10
Unfinished strings — 736 words Browse Translate Zen
10
Strings marked for edit — 736 words Browse Translate Zen
10
Unfinished strings without suggestions — 736 words Browse Translate Zen
1
Strings with any failing checks — 1 word Browse Translate Zen
1
Translated strings with any failing checks — 1 word Browse Translate Zen
1
Failing check: Inconsistent — 1 word Browse Translate Zen
93
Strings without a label — 6,345 words Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
books/arch-handbook/partii This component is linked to the Documentation/articles/bsdl-gpl repository. Fix this component to clear its alerts. BSD-2-Clause 0% 2 6 37 2 0 0 0
books/developers-handbook/policies/_index This component is linked to the Documentation/articles/bsdl-gpl repository. Fix this component to clear its alerts. This translation is locked. BSD-2-Clause 0% 93 2,145 13,148 91 2 0 0
books/handbook/colophon This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 3 25 166 3 0 0 0
books/arch-handbook/partiii This component is linked to the Documentation/articles/bsdl-gpl repository. Fix this component to clear its alerts. BSD-2-Clause 0% 2 4 30 2 1 0 0
books/handbook/wayland/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 135 4,028 26,832 135 0 0 0
books/fdp-primer/see-also/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 18 77 865 18 0 0 0
books/developers-handbook/kerneldebug/_index This component is linked to the Documentation/articles/bsdl-gpl repository. Fix this component to clear its alerts. BSD-2-Clause 0% 210 5,085 33,598 210 0 0 0
books/fdp-primer/rosetta/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 62 417 4,051 62 0 0 0
books/developers-handbook/partiv This component is linked to the Documentation/articles/bsdl-gpl repository. Fix this component to clear its alerts. BSD-2-Clause 0% 2 4 35 2 0 0 0
articles/license-guide/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 89 2,782 18,589 89 1 0 0
Browse all components

Overview

Project website docs.freebsd.org/en
Translation license BSD 2-Clause "Simplified" License
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Only chosen users can contribute.
  • The translation uses bilingual files.
File mask documentation/content/*/articles/vm-design/_index.po
Translation file Download documentation/content/es/articles/vm-design/_index.po
Last change May 21, 2023, 6:04 p.m.
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 93 6,345 36,561
Translated 89% 83 88% 5,609 88% 32,390
Needs editing 10% 10 11% 736 11% 4,171
Read-only 0% 0 0% 0 0% 0
Failing checks 1% 1 1% 1 1% 3
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

2 changes 0 changes 0 changes 4 changes 0 changes 0 changes 4 changes 0 changes 0 changes 0 changes 6 changes 0 changes 0 changes 0 changes 0 changes 2 changes 1 change 0 changes 0 changes 1 change 0 changes 0 changes 0 changes 23 changes
Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May

Quick numbers

6,345
Hosted words
93
Hosted strings
89%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

+98%
Hosted words
+100%
+100%
Hosted strings
—
+89%
Translated
—
—
Contributors
+100%
User avatar None

New strings to translate

Documentation / articles/vm-design/_index — Spanish

10 new strings to translate appeared to the translation. 11 days ago
User avatar None

Resource update

Documentation / articles/vm-design/_index — Spanish

The "documentation/content/es/articles/vm-design/_index.po" file was changed. 11 days ago
User avatar None

String updated in the repository

Documentation / articles/vm-design/_index — Spanish

FreeBSD has added complexity (the `pv_entry` scheme) to increase performance (to limit page table accesses to _only_ those pte's that need to be modified).
FreeBSD tiene más complejidad (el esquema de `pv_entry`) para mejorar el rendimiento (para limitar los accesos a la tabla de páginas _sólo_ a aquellos pte que necesitan ser modificados).
11 days ago
User avatar None

Source string changed

Documentation / articles/vm-design/_index — Spanish

FreeBSD has added complexity (the `pv_entry` scheme) in order to increase performance (to limit page table accesses to _only_ those pte's that need to be modified).
11 days ago
User avatar None

String updated in the repository

Documentation / articles/vm-design/_index — Spanish

Under Linux there is no such linked list. To remove all the hardware page table mappings for a `vm_page` linux must index into every VM object that _might_ have mapped the page. For example, if you have 50 processes all mapping the same shared library and want to get rid of page X in that library, you need to index into the page table for each of those 50 processes even if only 10 of them have actually mapped the page. So Linux is trading off the simplicity of its design against performance. Many VM algorithms which are O(1) or (small N) under FreeBSD wind up being O(N), O(N^2), or worse under Linux. Since the pte's representing a particular page in an object tend to be at the same offset in all the page tables they are mapped in, reducing the number of accesses into the page tables at the same pte offset will often avoid blowing away the L1 cache line for that offset, which can lead to better performance.
En Linux no existe dicha lista enlazada. Para eliminar todos los mapeos de tablas de páginas hardware para una `vm_page` linux debe acceder a cada objeto de Memoria Virtual que _podría_ haber mapeado la página. Por ejemplo, si tienes 50 procesos todos mapeando la misma biblioteca compartida y quieres eliminar la página X de esa biblioteca, necesitas acceder a la tabla de páginas de cada uno de esos 50 procesos incluso si sólo 10 de ellos han mapeado la página. Así que Linux está favoreciendo la simplicidad en el diseño por el rendimiento. Muchos algoritmos de Memoria Virtual que son O(1) o (una N pequeña) en FreeBSD terminan siendo O(N), O(N^2), o peor en Linux. Puesto que los pte que representan una página concreta en un objeto suelen estar en el mismo desplazamiento en todas las tablas de páginas en las que están mapeadas, reducir el número de accesos a las tablas de páginas en el mismo desplazamiento del pte evitará por lo general que se destruya la línea de caché L1 para ese desplazamiento, lo que puede conllevar un mejor rendimiento.
11 days ago
User avatar None

Source string changed

Documentation / articles/vm-design/_index — Spanish

Under Linux there is no such linked list. In order tTo remove all the hardware page table mappings for a `vm_page` linux must index into every VM object that _might_ have mapped the page. For example, if you have 50 processes all mapping the same shared library and want to get rid of page X in that library, you need to index into the page table for each of those 50 processes even if only 10 of them have actually mapped the page. So Linux is trading off the simplicity of its design against performance. Many VM algorithms which are O(1) or (small N) under FreeBSD wind up being O(N), O(N^2), or worse under Linux. Since the pte's representing a particular page in an object tend to be at the same offset in all the page tables they are mapped in, reducing the number of accesses into the page tables at the same pte offset will often avoid blowing away the L1 cache line for that offset, which can lead to better performance.
11 days ago
User avatar None

String updated in the repository

Documentation / articles/vm-design/_index — Spanish

`pv_entry` structures only represent pages mapped by the MMU (one `pv_entry` represents one pte). This means that when we need to remove all hardware references to a `vm_page` (to reuse the page for something else, page it out, clear it, dirty it, and so forth) we can simply scan the linked list of pv_entry's associated with that vm_page to remove or modify the pte's from their page tables.
Las estructuras `pv_entry` sólo representan páginas mapeadas por la MMU (una `pv_entry` representa una pte). Esto significa que cuando necesitamos eliminar todas las referencias hardware a la `vm_page` (para reutilizar la página para otra cosa, pasarla a disco, borrarla, marcarla como sucia y demás) podemos simplemente escanear la lista enlazada de estructuras `pv_entry` asociadas con esa `vm_page` y eliminar o modificar la pte de sus tablas de páginas.
11 days ago
User avatar None

Source string changed

Documentation / articles/vm-design/_index — Spanish

`pv_entry` structures only represent pages mapped by the MMU (one `pv_entry` represents one pte). This means that when we need to remove all hardware references to a `vm_page` (in order to reuse the page for something else, page it out, clear it, dirty it, and so forth) we can simply scan the linked list of pv_entry's associated with that vm_page to remove or modify the pte's from their page tables.
11 days ago
User avatar None

String updated in the repository

Documentation / articles/vm-design/_index — Spanish

A large percentage of page faults that occur are zero-fill faults. You can usually see this by observing the `vmstat -s` output. These occur when a process accesses pages in its BSS area. The BSS area is expected to be initially zero but the VM system does not bother to allocate any memory at all until the process actually accesses it. When a fault occurs the VM system must not only allocate a new page, it must zero it as well. To optimize the zeroing operation the VM system has the ability to pre-zero pages and mark them as such, and to request pre-zeroed pages when zero-fill faults occur. The pre-zeroing occurs whenever the CPU is idle but the number of pages the system pre-zeros is limited to avoid blowing away the memory caches. This is an excellent example of adding complexity to the VM system to optimize the critical path.
Un gran porcentaje de los fallos de página que se producen son fallos de rellenado de ceros. Habitualmente puedes verlo observando la salida del comando `vmstat -s`. Esto ocurre cuando un proceso accede a páginas de su área de BSS. Se espera que el área de BSS esté inicializada a cero pero el sistema de Memoria Virtual no se molesta en asignar ninguna memoria en absoluto hasta el momento en el que el proceso accede de verdad. Cuando se produce un fallo el sistema de Memoria Virtual no solo debe asignar una nueva página, tiene que inicializarla a cero también. Para optimizar la operación de rellenado de ceros el sistema de Memoria Virtual tiene la capacidad de pre-inicializar páginas a cero y marcarlas como tal, y solicitar páginas pre-inicializadas a cero cuando ocurre un fallo de rellenado de ceros. La pre-inicialización a cero ocurren cuando la CPU está ociosa pero el número de páginas que el sistema pre-inicializa a cero está limitado para evitar destrozar las cachés de memoria. Este es un ejemplo excelente de cómo añadir complejidad al sistema de Memoria Virtual para optimizar el camino crítico.
11 days ago
User avatar None

Source string changed

Documentation / articles/vm-design/_index — Spanish

A large percentage of page faults that occur are zero-fill faults. You can usually see this by observing the `vmstat -s` output. These occur when a process accesses pages in its BSS area. The BSS area is expected to be initially zero but the VM system does not bother to allocate any memory at all until the process actually accesses it. When a fault occurs the VM system must not only allocate a new page, it must zero it as well. To optimize the zeroing operation the VM system has the ability to pre-zero pages and mark them as such, and to request pre-zeroed pages when zero-fill faults occur. The pre-zeroing occurs whenever the CPU is idle but the number of pages the system pre-zeros is limited in order to avoid blowing away the memory caches. This is an excellent example of adding complexity to the VM system in order to optimize the critical path.
11 days ago
Browse all translation changes