Translation status

93 Strings 22%
Browse Translate
6,369 Words 4%

Strings status

93
All strings — 6,369 words Browse Edit Zen
21
Translated strings — 315 words Browse Edit Zen
72
Strings needing action — 6,054 words Browse Edit Zen
13
Not translated strings — 458 words Browse Edit Zen
59
Strings marked for edit — 5,596 words Browse Edit Zen
8
Strings with suggestions — 342 words Browse Edit Zen
64
Strings needing action without suggestions — 5,712 words Browse Edit Zen
60
Strings with any failing checks — 5,598 words Browse Edit Zen
1
Translated strings with any failing checks — 2 words Browse Edit Zen
1
Failed check: Unchanged translation — 2 words Browse Edit Zen
59
Failed check: Has been translated — 5,596 words Browse Edit Zen

Other components

Component Translated Untranslated Untranslated words Untranslated characters Checks Suggestions Comments
books/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 2 4 35 0 0 0
books/porters-handbook/porting-samplem/chapter This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 21 474 3,299 2 1 0
articles/contributors/contrib-committers This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 398 398 2,867 0 0 0
books/developers-handbook/l10n/chapter This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 55 1,398 8,923 3 3 0
books/arch-handbook/vm/chapter This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 36 1,761 10,704 1 1 0
books/arch-handbook/newbus/chapter This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 65 1,597 10,451 4 4 0
books/handbook/partv This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 2 4 29 1 1 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 4 0 0
books/handbook/colophon This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 3 25 166 0 0 0
books/developers-handbook/testing/chapter This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 86 1,717 10,972 1 1 0
Browse all components

Overview

Project website docs.freebsd.org/en
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 "Simplified" License
Filemask documentation/content/*/articles/vm-design/_index.po
Translation file Download documentation/content/pt_BR/articles/vm-design/_index.po
Last change May 30, 2021, 9:44 p.m.
Last author Danilo G. Baio

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 93 6,369 36,669
Translated 22% 21 4% 315 5% 1,970
Needs editing 63% 59 87% 5,596 87% 32,126
Failing checks 64% 60 87% 5,598 87% 32,139
Strings with suggestions 8% 8 5% 342 5% 1,965
Not translated strings 13% 13 7% 458 7% 2,573
Last year Previous

Activity in last 12 months

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

Quick numbers

6,369
Hosted words
93
Hosted strings
22%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+1%
—
Hosted strings
+1%
—
Translated
-1%
—
Contributors
—
User avatar dbaio

New string to translate

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

New string to translate a month ago
User avatar dbaio

Resource update

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

Resource update a month ago
User avatar dbaio

Translation changed

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

Abstract
SumáriResumo
2 months ago
User avatar None

Automatic translation

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

The title is really just a fancy way of saying that I am going to attempt to describe the whole VM enchilada, hopefully in a way that everyone can follow. For the last year I have concentrated on a number of major kernel subsystems within FreeBSD, with the VM and Swap subsystems being the most interesting and NFS being "a necessary chore". I rewrote only small portions of the code. In the VM arena the only major rewrite I have done is to the swap subsystem. Most of my work was cleanup and maintenance, with only moderate code rewriting and no major algorithmic adjustments within the VM subsystem. The bulk of the VM subsystem's theoretical base remains unchanged and a lot of the credit for the modernization effort in the last few years belongs to John Dyson and David Greenman. Not being a historian like Kirk I will not attempt to tag all the various features with peoples names, since I will invariably get it wrong.
O título é realmente apenas uma maneira extravagante de dizer que vou tentar descrever todo o grupo de itens de uma VM, espero que de uma forma que todos possam acompanhar. Pelo ultimo ano eu me concentrei em vários dos principais subsistemas do kernel dentro do FreeBSD, com os subsistemas VM e Swap sendo os mais interessantes e o NFS sendo <quote>uma tarefa necessária</quote>. Eu reescrevi apenas pequenas partes do código. Na área de VM, a única grande reescrita que fiz foi para o subsistema de troca. A maior parte do meu trabalho foi de limpeza e manutenção, com apenas uma moderada reescrita de código e sem grandes ajustes nos algorítimos do subsistema VM. A maior parte da base teórica do subsistema VM permanece inalterada e muito do crédito pelo esforço de modernização nos últimos anos pertence a John Dyson e David Greenman. Não sendo um historiador como Kirk, eu não tentarei marcar todos os vários recursos com nomes de pessoas, já que invariavelmente vou errar.
3 months ago
User avatar None

New contributor

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

New contributor 3 months ago
User avatar None

Automatic translation

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

Before moving along to the actual design let's spend a little time on the necessity of maintaining and modernizing any long-living codebase. In the programming world, algorithms tend to be more important than code and it is precisely due to BSD's academic roots that a great deal of attention was paid to algorithm design from the beginning. More attention paid to the design generally leads to a clean and flexible codebase that can be fairly easily modified, extended, or replaced over time. While BSD is considered an "old" operating system by some people, those of us who work on it tend to view it more as a "mature" codebase which has various components modified, extended, or replaced with modern code. It has evolved, and FreeBSD is at the bleeding edge no matter how old some of the code might be. This is an important distinction to make and one that is unfortunately lost to many people. The biggest error a programmer can make is to not learn from history, and this is precisely the error that many other modern operating systems have made. Windows NT(R) is the best example of this, and the consequences have been dire. Linux also makes this mistake to some degree-enough that we BSD folk can make small jokes about it every once in a while, anyway. Linux's problem is simply one of a lack of experience and history to compare ideas against, a problem that is easily and rapidly being addressed by the Linux community in the same way it has been addressed in the BSD community-by continuous code development. The Windows NT(R) folk, on the other hand, repeatedly make the same mistakes solved by UNIX(R) decades ago and then spend years fixing them. Over and over again. They have a severe case of "not designed here" and "we are always right because our marketing department says so". I have little tolerance for anyone who cannot learn from history.
Antes de avançarmos para o design atual, vamos dedicar um pouco de tempo a necessidade de manter e modernizar qualquer base de código duradoura. No mundo da programação, os algoritmos tendem a ser mais importantes do que o código, e é precisamente devido as raízes acadêmicas do BSD que uma grande atenção foi dada ao design do algoritmo desde o início. Mais atenção ao design geralmente leva a uma base de código limpa e flexível que pode ser facilmente modificada, estendida ou substituída ao longo do tempo. Embora o BSD seja considerado um sistema operacional <quote>antigo</quote> por algumas pessoas, aqueles de nós que trabalham nele tendem a vê-lo mais como uma base de código <quote>madura</quote> que possui vários componentes modificados, estendidos, ou substituído por código moderno. Ele evoluiu e o FreeBSD está no topo, não importa quantos anos tenha o código. Esta é uma distinção importante a ser feita e infelizmente perdida para muitas pessoas. O maior erro que um programador pode cometer é não aprender com a história, e esse é precisamente o erro que muitos outros sistemas operacionais modernos cometeram. <trademark class="registered">Windows NT</trademark> é o melhor exemplo disso, e as conseqüências foram terríveis. O Linux também cometeu esse erro até certo ponto - o suficiente para que nós, do BSD, possamos fazer pequenas piadas sobre isso de vez em quando, entretanto. O problema do Linux é simplesmente a falta de experiência e histórico para comparar idéias, um problema que está sendo resolvido de forma fácil e rápida pela comunidade Linux, da mesma forma como foi abordado na comunidade BSD - pelo desenvolvimento contínuo de código. Por outro lado, o povo do <trademark class="registered">Windows NT</trademark>, repetidamente comete os mesmos erros resolvidos no <trademark class="registered">UNIX</trademark> décadas atrás e depois gasta anos corrigindo-os. De novo e de novo. Eles têm um caso grave de <quote>não foi projetado aqui</quote> e <quote>estamos sempre certos porque nosso departamento de marketing diz que sim</quote>. Tenho pouca tolerância para quem não pode aprender com a história.
3 months ago
User avatar None

New contributor

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

New contributor 3 months ago
User avatar None

Automatic translation

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

Much of the apparent complexity of the FreeBSD design, especially in the VM/Swap subsystem, is a direct result of having to solve serious performance issues that occur under various conditions. These issues are not due to bad algorithmic design but instead rise from environmental factors. In any direct comparison between platforms, these issues become most apparent when system resources begin to get stressed. As I describe FreeBSD's VM/Swap subsystem the reader should always keep two points in mind:
Grande parte da complexidade aparente do design do FreeBSD, especialmente no subsistema VM/Swap, é um resultado direto de ter que resolver sérios problemas de desempenho que ocorrem sob várias condições. Estes problemas não se devem ao mau design de algorítimo, mas sim a fatores ambientais. Em qualquer comparação direta entre plataformas, estes problemas tornam-se mais aparentes quando os recursos do sistema começam a ficar estressados. Como descrevo o subsistema VM/Swap do FreeBSD, o leitor deve sempre manter dois pontos em mente:
3 months ago
User avatar None

New contributor

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

New contributor 3 months ago
User avatar None

Automatic translation

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

The most important aspect of performance design is what is known as "Optimizing the Critical Path". It is often the case that performance optimizations add a little bloat to the code in order to make the critical path perform better.
O aspecto mais importante do design de desempenho é o que é conhecido como <quote>Otimizando o Caminho Crítico </quote>. Muitas vezes, as otimizações de desempenho inflam um pouco o código, para que o caminho crítico tenha um melhor desempenho.
3 months ago
Browse all translation changes