概览

项目网站 docs.freebsd.org/en
翻译许可证 BSD 2-Clause "Simplified" License
翻译进程
  • 可以直接翻译。
  • 可以提出翻译建议。
  • 只允许指定的用户贡献。
  • 该翻译使用双语文件。
文件掩码 documentation/content/*/articles/geom-class/_index.po
翻译文件 下载 documentation/content/pt/articles/geom-class/_index.po
最后更改 None
最后作者 None

字符串统计数据

字符串百分比 托管的字符串数 字数百分比 托管的单词数 字符百分比 托管的字符数
总数 146 2960 18956
已翻译数 0% 0 0% 0 0% 0
需要编辑 0% 0 0% 0 0% 0
只读 0% 0 0% 0 0% 0
未通过的检查数 0% 0 0% 0 0% 0
带有建议的字符串数 0% 0 0% 0 0% 0
未翻译的字符串数 100% 146 100% 2960 100% 18956
过去 12 个月 上一年

过去 12 个月内的活动

0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 149 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改
十月 十一月 十二月 一月 二月 三月 四月 五月 六月 七月 八月 九月

快速数字

2960
托管的单词数
146
托管的字符串数
0%
已翻译
0
贡献者
及之前 30 天

过去 30 天的趋势

—
托管的单词数
+100%
—
托管的字符串数
+100%
—
已翻译
—
—
贡献者
—
用户头像 无

提交了更改

Documentation / articles/geom-class/_index — 葡萄牙语

提交了更改 1 年前
用户头像 无

要翻译的新字符串

Documentation / articles/geom-class/_index — 葡萄牙语

翻译中出现了 146 条要翻译的新字符串。 1 年前
用户头像 无

资源更新

Documentation / articles/geom-class/_index — 葡萄牙语

添加了文件 documentation/content/pt/articles/geom-class/_index.po。 1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/geom-class/_index — 葡萄牙语

Mutexes in FreeBSD kernel (see man:mutex[9]) have one distinction from their more common userland cousins - the code cannot sleep while holding a mutex). If the code needs to sleep a lot, man:sx[9] locks may be more appropriate. On the other hand, if you do almost everything in a single thread, you may get away with no mutexes at all.
 
1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/geom-class/_index — 葡萄牙语

The other benefit of having a event-handler thread like that is to serialize all the requests and responses coming from different geom threads into one thread. This is also very convenient but can be slow. In most cases, handling of `.done`() requests can be left to the `g_up` thread.
 
1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/geom-class/_index — 葡萄牙语

The main benefit of using a thread to handle I/O requests is that it can sleep when needed. Now, this sounds good, but should be carefully thought out. Sleeping is well and very convenient but can very effectively destroy performance of the geom transformation. Extremely performance-sensitive classes probably should do all the work in `.start`() function call, taking great care to handle out-of-memory and similar errors.
 
1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/geom-class/_index — 葡萄牙语

In GEOM code, the usual use of threads is to offload processing of requests from `g_down` thread (the `.start`() function). These threads look like "event handlers": they have a linked list of event associated with them (on which events can be posted by various functions in various threads so it must be protected by a mutex), take the events from the list one by one and process them in a big `switch`() statement.
 
1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/geom-class/_index — 葡萄牙语

Kernel threads are created with man:kthread_create[9] function, and they are sort of similar to userland threads in behavior, only they cannot return to caller to signify termination, but must call man:kthread_exit[9].
 
1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/geom-class/_index — 葡萄牙语

Kernel Threads for Use in GEOM Code
 
1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/geom-class/_index — 葡萄牙语

This restriction is here to stop GEOM code clogging the I/O request path, since sleeping is usually not time-bound and there can be no guarantees on how long will it take (there are some other, more technical reasons also). It also means that there is not much that can be done in those threads; for example, almost any complex thing requires memory allocation. Fortunately, there is a way out: creating additional kernel threads.
 
1 年前
浏览翻译的所有变化