Translation status

93 Strings 21%
Browse Translate
6,345 Words 4%

Strings status

93
All strings — 6,345 words Browse Translate Zen
20
Translated strings — 263 words Browse Translate Zen
73
Unfinished strings — 6,082 words Browse Translate Zen
13
Untranslated strings — 456 words Browse Translate Zen
60
Strings marked for edit — 5,626 words Browse Translate Zen
5
Strings with suggestions — 208 words Browse Translate Zen
68
Unfinished strings without suggestions — 5,874 words Browse Translate Zen
51
Strings with any failing checks — 4,759 words Browse Translate Zen
1
Translated strings with any failing checks — 2 words Browse Translate Zen
1
Failing check: Unchanged translation — 2 words Browse Translate Zen
50
Failing check: Has been translated — 4,757 words 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/_index 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
books/handbook/partv This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 2 4 29 1 1 1 0
books/developers-handbook/l10n/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 56 1,407 9,030 53 3 0 0
books/arch-handbook/newbus/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 65 1,597 10,451 61 4 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/developers-handbook/testing/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 86 1,717 10,980 85 1 0 0
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 1 1 0 0
books/arch-handbook/vm/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 37 1,766 10,736 36 1 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
books/porters-handbook/porting-samplem/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 21 450 3,180 20 0 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/pt_BR/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 21% 20 4% 263 4% 1,664
Needs editing 64% 60 88% 5,626 88% 32,333
Read-only 0% 0 0% 0 0% 0
Failing checks 54% 51 75% 4,759 74% 27,411
Strings with suggestions 5% 5 3% 208 3% 1,197
Untranslated strings 13% 13 7% 456 7% 2,564
Last 12 months Previous

Activity in last 12 months

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

Quick numbers

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

Trends of last 30 days

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

New strings to translate

Documentation / articles/vm-design/_index — Portuguese (Brazil)

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

Resource update

Documentation / articles/vm-design/_index — Portuguese (Brazil)

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

String updated in the repository

Documentation / articles/vm-design/_index — Portuguese (Brazil)

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).
 
8 days ago
User avatar None

String updated in the repository

Documentation / articles/vm-design/_index — Portuguese (Brazil)

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.
No Linux, não existe essa lista vinculada. Para remover todos os mapeamentos de tabelas de páginas de hardware para um <literal>vm_page</literal>, o linux deve indexar em todos os objetos de VM que <emphasis>possam</emphasis> ter mapeado a página. Por exemplo, se você tiver 50 processos, todos mapeando a mesma biblioteca compartilhada e quiser se livrar da página X nessa biblioteca, será necessário indexar na tabela de páginas para cada um desses 50 processos, mesmo se apenas 10 deles realmente tiverem mapeado a página. Então, o Linux está trocando a simplicidade de seu design com o desempenho. Muitos algoritmos de VM que são O(1) ou (pequeno N) no FreeBSD acabam sendo O(N), O(N^2), ou pior no Linux. Como os pte's que representam uma determinada página em um objeto tendem a estar no mesmo offset em todas as tabelas de páginas em que estão mapeados, reduzir o número de acessos nas tabelas de páginas no mesmo pte offset evitará a linha de cache L1 para esse deslocamento, o que pode levar a um melhor desempenho.
8 days ago
User avatar None

String updated in the repository

Documentation / articles/vm-design/_index — Portuguese (Brazil)

`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.
As estruturas <literal>pv_entry</literal> representam apenas as páginas mapeadas pela MMU (uma <literal>pv_entry</literal> representa uma pte). Isso significa que quando precisamos remover todas as referências de hardware para uma <literal>vm_page</literal> (para reutilizar a página para outra coisa, paginar, limpar, inativar e assim por diante), podemos simplesmente escanear a lista encadeada de <literal>pv_entry</literal> associada a essa <literal>vm_page</literal> para remover ou modificar os pte's de suas tabelas de páginas.
8 days ago
User avatar None

String updated in the repository

Documentation / articles/vm-design/_index — Portuguese (Brazil)

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.
Uma grande porcentagem de falhas de página que ocorrem são falhas de preenchimento com zero. Geralmente, você pode ver isso observando a saída de <command>vmstat -s</command>. Estas falhas ocorrem quando um processo acessa páginas em sua área BSS. Espera-se que a área BSS seja inicialmente zero, mas o sistema de VM não se preocupa em alocar memória alguma até que o processo realmente a acesse. Quando ocorre uma falha, o sistema de VM deve alocar não apenas uma nova página, mas deve zerá-la também. Para otimizar a operação de zeramento, o sistema de VM tem a capacidade de pré-zerar páginas e marcá-las como tal, e solicitar páginas pré-zeradas quando ocorrem falhas de preenchimento com zero. O pré-zeramento ocorre sempre que a CPU está inativa, mas o número de páginas que o sistema pre-zeros é limitado, a fim de evitar que os caches de memória sejam dissipados. Este é um excelente exemplo de adição de complexidade ao sistema de VM para otimizar o caminho crítico.
8 days ago
User avatar None

String updated in the repository

Documentation / articles/vm-design/_index — Portuguese (Brazil)

An urban myth has circulated for years that Linux did a better job avoiding swapouts than FreeBSD, but this in fact is not true. What was actually occurring was that FreeBSD was proactively paging out unused pages to make room for more disk cache while Linux was keeping unused pages in core and leaving less memory available for cache and process pages. I do not know whether this is still true today.
Uma lenda urbana circulou durante anos que o Linux fez um trabalho melhor evitando trocas do que o FreeBSD, mas isso de fato não é verdade. O que estava realmente ocorrendo era que o FreeBSD estava proativamente numerando páginas não usadas a fim de abrir espaço para mais cache de disco enquanto o Linux mantinha páginas não utilizadas no núcleo e deixando menos memória disponível para páginas de cache e processo. Eu não sei se isso ainda é verdade hoje.
8 days ago
User avatar None

String updated in the repository

Documentation / articles/vm-design/_index — Portuguese (Brazil)

How much overhead are we willing to suffer in the critical path to avoid freeing the wrong page? Each wrong choice we make will cost us hundreds of thousands of CPU cycles and a noticeable stall of the affected processes, so we are willing to endure a significant amount of overhead to be sure that the right page is chosen. This is why FreeBSD tends to outperform other systems when memory resources become stressed.
Quanta sobrecarga estamos dispostos a sofrer no caminho crítico para evitar a liberação da página errada? Cada escolha errada que fazemos nos custará centenas de milhares de ciclos da CPU e uma paralisação notável dos processos afetados, por isto estamos dispostos a suportar uma quantidade significativa de sobrecarga, a fim de ter certeza de que a página certa é escolhida. É por isto que o FreeBSD tende a superar outros sistemas quando os recursos de memória ficam estressados.
8 days ago
User avatar None

String updated in the repository

Documentation / articles/vm-design/_index — Portuguese (Brazil)

I did not take the final step of having an "allocating hint pointer" that would trundle through a portion of swap as allocations were made to further guarantee contiguous allocations or at least locality of reference, but I ensured that such an addition could be made.
Eu não dei o último passo de ter um <quote>ponteiro de sugestão de alocação</quote> que percorria uma porção da swap conforme as alocações eram feitas a fim de garantir alocações contíguas ou pelo menos a referência localmente, mas assegurei que tal adição poderia ser feita.
8 days ago
User avatar None

String updated in the repository

Documentation / articles/vm-design/_index — Portuguese (Brazil)

The entire radix tree bitmap is also preallocated to avoid having to allocate kernel memory during critical low memory swapping operations. After all, the system tends to swap when it is low on memory so we should avoid allocating kernel memory at such times to avoid potential deadlocks.
Todo o bitmap da árvore raiz também é pré-alocado para evitar ter que alocar a memória do kernel durante operações críticas de troca com memória baixa. Afinal de contas, o sistema tende a trocar quando está com pouca memória, por isso devemos evitar a alocação da memória do kernel nesses momentos para evitar possíveis deadlocks.
8 days ago
Browse all translation changes