FreeBSD Doc (Archived)/articles

Project locked to follow the migration to Hugo/AsciiDoctor, sorry for the inconvenience and please wait a few days to continue with the translations.

The translation is temporarily closed for contributions due to maintenance, please come back later.

Language	Translated	Untranslated	Untranslated words	Untranslated characters	Checks	Suggestions	Comments
English BSD-2-Clause-FreeBSD		0	0	0	6	0	0

Portuguese (Brazil) BSD-2-Clause-FreeBSD	98%	2	55	313	12	0	0

Spanish BSD-2-Clause-FreeBSD		0	0	0	7	2	4

Please sign in to see the alerts.

Overview

Project website	wiki.freebsd.org/DocTranslationOnWeblate
Instructions for translators	https://wiki.freebsd.org/DocTranslationOnWeblate Mailing list for translators: <<freebsd-translators@freebsd.org>
Translation process	Translations can be made directly. Translation suggestions can be made. Only chosen users can contribute. The translation uses bilingual files.
Translation license	BSD-2-Clause-FreeBSD
Filemask	`articles/*/vm-design.po`

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		324		20,043		121,899
Source		108		6,681		40,633
Translated	99%	322	99%	19,988	99%	121,586
Needs editing	1%	1	1%	54	1%	304
Failing checks	7%	25	4%	982	5%	6,678
Strings with suggestions	1%	2	1%	97	1%	593
Not translated strings	1%	1	1%	1	1%	9

Last year Previous

Activity in last 12 months


Oct	Nov	Dec	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep

Quick numbers

20,043

Hosted words

324

Hosted strings

99%

Translated

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

—

Hosted strings

—

Translated

—

Contributors

+100%

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2021-09-23 AND NOT changed_by:anonymous`	Add
Translated strings	`state:>=translated`	Add
Strings with comments	`has:comment`	Add
Strings with any failing checks	`has:check`	Add
Strings with suggestions from others	`has:suggestion AND NOT suggestion_author:anonymous`	Add
Approved strings with suggestions	`state:approved AND has:suggestion`	Add
All untranslated strings added the past month	`added:>=2021-09-23 AND state:<=needs-editing`	Add
Translated strings in a certain language	`is:translated AND language:en`	Add

None

Resource update

FreeBSD Doc (Archived) / articles_vm-design — Portuguese (Brazil)

Resource update a month ago

None

Resource update

FreeBSD Doc (Archived) / articles_vm-design — Spanish

Resource update a month ago

None

Resource update

FreeBSD Doc (Archived) / articles_vm-design — English

Resource update a month ago

None

Resource update

FreeBSD Doc (Archived) / articles_vm-design — Portuguese (Brazil)

Resource update a month ago

None

Resource update

FreeBSD Doc (Archived) / articles_vm-design — Spanish

Resource update a month ago

None

Resource update

FreeBSD Doc (Archived) / articles_vm-design — English

Resource update a month ago

None

New alert

FreeBSD Doc (Archived) / articles_vm-design

Broken project website URL 4 months ago

dbaio

Component locked

FreeBSD Doc (Archived) / articles_vm-design

Component locked 8 months ago

fernape

Translation changed

FreeBSD Doc (Archived) / articles_vm-design — Spanish

English

FreeBSD manages all of this with a layered VM Object model. The original binary program file winds up being the lowest VM Object layer. A copy-on-write layer is pushed on top of that to hold those pages which had to be copied from the original file. If the program modifies a data page belonging to the original file the VM system takes a fault and makes a copy of the page in the higher layer. When a process forks, additional VM Object layers are pushed on. This might make a little more sense with a fairly basic example. A <function>fork()</function> is a common operation for any *BSD system, so this example will consider a program that starts up, and forks. When the process starts, the VM system creates an object layer, let's call this A:

Spanish 5 characters edited Current translation

FreeBSD gestinoa todo esto con un modelo de Objetos de Memoria Virtual en capas. El fichero del programa binario original termina siendo la capa de Objetos de Memoria Virtual más baja. Una capa copy-on-write se sitúa encima de ella para mantener aquellas páginas que han sido copiadas del fichero original. Si el programa modifica una página de datos que pertenece al fichero original el sistema de Memoria Virtual ~~genera~~recibe un fallo de página y hace una copia de la página en la capa superior. Cuando un proceso bifurca, se empujan nuevas capas de Objetos de Memoria Virtual. Esto puede cobrar más sentido con un ejemplo bastante básico. Un <function>fork()</function> es una operación común para cualquier sistema *BSD, así que este ejemplo considerará un programa que arranca, y bifurca. Cuando el proceso arranca, el sistema de Memoria Virtual crea una capa de objetos, llamémosla A:

9 months ago

fernape

New translation

FreeBSD Doc (Archived) / articles_vm-design — Spanish

English

Note that I say <quote>reasonably</quote> contiguous rather than simply <quote>contiguous</quote>. From the point of view of a 128K direct mapped cache, the physical address 0 is the same as the physical address 128K. So two side-by-side pages in your virtual address space may wind up being offset 128K and offset 132K in physical memory, but could also easily be offset 128K and offset 4K in physical memory and still retain the same cache performance characteristics. So page-coloring does <emphasis>not</emphasis> have to assign truly contiguous pages of physical memory to contiguous pages of virtual memory, it just needs to make sure it assigns contiguous pages from the point of view of cache performance and operation.

Spanish

Nótese que digo <quote>razonablemente</quote> contiguas en lugar de simplemente <quote>contiguas</quote>. Desde el punto de vista de una caché de mapeo directo de 128K, la dirección física 0 es la misma que la dirección física 128K. De modo que dos páginas una al lado de la otra en tu espacio de memoria virtual podrían terminar siendo el desplazamiento 128K y 132K en memoria física, pero podría fácilmente ser también el desplazamiento 128K y 4K en memoria física y mantener todavía las mismas características de rendimiento de la caché. Así que el coloreado de páginas <emphasis>no</emphasis> tiene que asignar páginas de memoria física realmente contiguas a páginas de memoria virtual que sí lo son, sólo necesita asegurarse de que asigna páginas contiguas desde el punto de vista del rendimiento y la operativa de la caché.

9 months ago

Browse all component changes