Documentation/articles/geom-class/

Language	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
English BSD-2-Clause		0	0	0	0	15	0	0

Chinese (Simplified) (zh_CN) BSD-2-Clause	2%	143	2,957	18,933	143	0	0	0

Chinese (Traditional) (zh_TW) BSD-2-Clause	2%	143	2,957	18,933	143	0	0	0

Dutch (nl_NL) BSD-2-Clause	1%	145	2,959	18,944	145	1	0	0

French BSD-2-Clause	0%	146	2,960	18,956	146	0	0	0

French (fr_FR) BSD-2-Clause	1%	144	2,958	18,941	144	0	0	0

German (de_DE) BSD-2-Clause	2%	143	2,957	18,933	143	0	0	0

Greek BSD-2-Clause	2%	143	2,957	18,933	143	0	0	0

Indonesian BSD-2-Clause	0%	146	2,960	18,956	146	0	0	0

Italian (it_IT) BSD-2-Clause	1%	144	2,958	18,936	144	0	0	0

Korean BSD-2-Clause	2%	143	2,957	18,933	143	0	0	0

Norwegian Bokmål BSD-2-Clause	1%	145	2,959	18,944	145	0	0	0

Persian BSD-2-Clause	2%	143	2,957	18,933	143	0	0	0

Polish BSD-2-Clause	2%	143	2,957	18,933	143	0	0	0

Portuguese BSD-2-Clause	0%	146	2,960	18,956	146	0	0	0

Portuguese (Brazil) BSD-2-Clause		0	0	0	0	0	0	0

Spanish BSD-2-Clause		0	0	0	0	0	0	0

Turkish (tr_TR) BSD-2-Clause	0%	146	2,960	18,956	145	1	0	0

Please sign in to see the alerts.

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/geom-class/_index.po`

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		2,628		53,280		341,208
Source		146		2,960		18,956
Translated	17%	465	16%	8,907	16%	57,088
Needs editing	1%	1	1%	1	1%	8
Read-only	5%	146	5%	2,960	5%	18,956
Failing checks	1%	17	1%	42	1%	488
Strings with suggestions	0%	0	0%	0	0%	0
Untranslated strings	82%	2,162	83%	44,372	83%	284,112

Last 12 months Previous

Activity in last 12 months


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

Quick numbers

53,280

Hosted words

2,628

Hosted strings

17%

Translated

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

+100%

—

Hosted strings

+100%

—

Translated

+17%

—

Contributors

+100%

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2025-02-26 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:>=2025-02-26 AND state:<=needs-editing`	Add
Translated strings in a certain language	`is:translated AND language:en`	Add

None Committed changes Documentation / articles/geom-class/_index — French	Committed changes 2 months ago
None New strings to translate Documentation / articles/geom-class/_index — French	146 new strings to translate appeared to the translation. 2 months ago
None Resource update Documentation / articles/geom-class/_index — French	File `documentation/content/fr/articles/geom-class/_index.po` was added. 2 months ago
None String updated in the repository Documentation / articles/geom-class/_index — French	English 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. French 0 characters edited Current translation 2 months ago
None String updated in the repository Documentation / articles/geom-class/_index — French	English 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. French 0 characters edited Current translation 2 months ago
None String updated in the repository Documentation / articles/geom-class/_index — French	English 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. French 0 characters edited Current translation 2 months ago
None String updated in the repository Documentation / articles/geom-class/_index — French	English 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. French 0 characters edited Current translation 2 months ago
None String updated in the repository Documentation / articles/geom-class/_index — French	English 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]. French 0 characters edited Current translation 2 months ago
None String updated in the repository Documentation / articles/geom-class/_index — French	English Kernel Threads for Use in GEOM Code French 0 characters edited Current translation 2 months ago
None String updated in the repository Documentation / articles/geom-class/_index — French	English 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. French 0 characters edited Current translation 2 months ago

Browse all component changes