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 Checks Suggestions Comments
English This translation is used for source strings. This component is linked to the FreeBSD Doc (Archived)/articles_bsdl-gpl repository. This translation is locked. BSD-2-Clause-FreeBSD 54
Portuguese (Brazil) This component is linked to the FreeBSD Doc (Archived)/articles_bsdl-gpl repository. This translation is locked. BSD-2-Clause-FreeBSD 98% 5 377 17
Spanish This component is linked to the FreeBSD Doc (Archived)/articles_bsdl-gpl repository. This translation is locked. BSD-2-Clause-FreeBSD 86% 50 596 69 1
Start new translation
Please sign in to see the alerts.
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/*/linux-emulation.po
Languages 3
Source strings 384
Source words 12,594
Source characters 96,878
Hosted strings 1,152
Hosted words 37,782
Hosted characters 290,634
Component locked 4 weeks ago
New strings to translate a month ago
New strings to translate a month ago
Resource update a month ago
Threaded programs should be written with as little contention on locks as possible. Otherwise, instead of doing useful work the thread just waits on a lock. BecauseAs a result of this, the most well written threaded programs show little locks contention.
a month ago
The locking is implemented to be per-subsystem because we do not expect a lot of contention on these. There are two locks: <literal>emul_lock</literal> used to protect manipulating of <literal>linux_emuldata</literal> and <literal>emul_shared_lock</literal> used to manipulate <literal>linux_emuldata_shared</literal>. The <literal>emul_lock</literal> is a nonsleepable blocking mutex while <literal>emul_shared_lock</literal> is a sleepable blocking <literal>sx_lock</literal>. Because ofDue to the per-subsystem locking we can coalesce some locks and that is why the em find offers the non-locking access.
a month ago
Because of the describedAs there is a differentce in view knowing whatas what to the idea of a process ID and thread ID is between FreeBSD and <trademark class="registered">Linux</trademark> we have to translate the view somehow. We do it by PID mangling. This means that we fake what a PID (=TGID) and TID (=PID) is between kernel and userland. The rule of thumb is that in kernel (in Linuxulator) PID = PID and TGID = shared -&gt; group pid and to userland we present <literal>PID = shared -&gt; group_pid</literal> and <literal>TID = proc -&gt; p_pid</literal>. The PID member of <literal>linux_emuldata structure</literal> is a FreeBSD PID.
a month ago
There are currently two ways to implement threading in FreeBSD. The first way is M:N threading followed by the 1:1 threading model. The default library used is M:N threading (<literal>libpthread</literal>) and you can switch at runtime to 1:1 threading (<literal>libthr</literal>). The plan is to switch to 1:1 library by default soon. Although those two libraries use the same kernel primitives, they are accessed through different API(es). The M:N library uses the <literal>kse_*</literal> family of syscalls while the 1:1 library uses the <literal>thr_*</literal> family of syscalls. Because ofDue to this, there is no general concept of thread ID shared between kernel and userspace. Of course, both threading libraries implement the pthread thread ID API. Every kernel thread (as described by <literal>struct thread</literal>) has td tid identifier but this is not directly accessible from userland and solely serves the kernel's needs. It is also used for 1:1 threading library as pthread's thread ID but handling of this is internal to the library and cannot be relied on.
a month ago
Resource update a month ago
User avatar None

Source string changed

FreeBSD Doc (Archived) / articles_linux-emulationSpanish

Threaded programs should be written with as little contention on locks as possible. Otherwise, instead of doing useful work the thread just waits on a lock. BecauseAs a result of this, the most well written threaded programs show little locks contention.
a month ago
Browse all component changes

Daily activity

Daily activity

Weekly activity

Weekly activity