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/linux-emulation/_index.po
Translation file Download documentation/content/fa/articles/linux-emulation/_index.po
Last change May 30, 2021, 9:16 p.m.
Last author Parsa Samet

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 396 12,240 77,383
Translated 1% 4 1% 4 1% 32
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 98% 392 99% 12,236 99% 77,351
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 3 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 0 changes
Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug

Quick numbers

12,240
Hosted words
396
Hosted strings
1%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

New string to translate

Documentation / articles/linux-emulation/_index — Persian

1 new string to translate appeared in the translation. a year ago
User avatar None

Resource update

Documentation / articles/linux-emulation/_index — Persian

The "documentation/content/fa/articles/linux-emulation/_index.po" file was changed. a year ago
User avatar None

String updated in the repository

Documentation / articles/linux-emulation/_index — Persian

Common UNIX(R) API defines a syscall as a way to issue commands from a user space process to the kernel. The most common implementation is either by using an interrupt or specialized instruction (think of `SYSENTER`/`SYSCALL` instructions for ia32). Syscalls are defined by a number. For example in FreeBSD, the syscall number 85 is the man:swapon[2] syscall and the syscall number 132 is man:mkfifo[2]. Some syscalls need parameters, which are passed from the user-space to the kernel-space in various ways (implementation dependent). Syscalls are synchronous.
 
a year ago
User avatar None

New strings to translate

Documentation / articles/linux-emulation/_index — Persian

6 new strings to translate appeared to the translation. 2 years ago
User avatar None

Resource update

Documentation / articles/linux-emulation/_index — Persian

The "documentation/content/fa/articles/linux-emulation/_index.po" file was changed. 2 years ago
User avatar None

String updated in the repository

Documentation / articles/linux-emulation/_index — Persian

Many UNIX(R) derivates implement the man:ptrace[2] syscall to allow various tracking and debugging features. This facility enables the tracing process to obtain various information about the traced process, like register dumps, any memory from the process address space, etc. and also to trace the process like in stepping an instruction or between system entries (syscalls and traps). man:ptrace[2] also lets you set various information in the traced process (registers etc.). man:ptrace[2] is a UNIX(R)-wide standard implemented in most UNIX(R)es around the world.
 
2 years ago
User avatar None

String updated in the repository

Documentation / articles/linux-emulation/_index — Persian

The Linux(R) emulation layer is not complete, as some syscalls are not implemented properly and some are not implemented at all. The emulation layer employs a facility to mark unimplemented syscalls with the `DUMMY` macro. These dummy definitions reside in [.filename]#linux_dummy.c# in a form of `DUMMY(syscall);`, which is then translated to various syscall auxiliary files and the implementation consists of printing a message saying that this syscall is not implemented. The `UNIMPL` prototype is not used because we want to be able to identify the name of the syscall that was called to know what syscalls are more important to implement.
 
2 years ago
User avatar None

String updated in the repository

Documentation / articles/linux-emulation/_index — Persian

`sched_bind` is an API used to bind a thread to a particular CPU for all the time it executes the code, until a `sched_unbind` function call does not unbind it. This feature has a key role in situations where you cannot trust the current state of CPUs (for example, at very early stages of boot), as you want to avoid your thread to migrate on inactive CPUs. Since `sched_bind` and `sched_unbind` manipulate internal scheduler structures, they need to be enclosed in `sched_lock` acquisition/releasing when used.
 
2 years ago
User avatar None

String updated in the repository

Documentation / articles/linux-emulation/_index — Persian

The FreeBSD kernel has been made preemptive basically to deal with interrupt threads. In fact, to avoid high interrupt latency, time-sharing priority threads can be preempted by interrupt threads (in this way, they do not need to wait to be scheduled as the normal path previews). Preemption, however, introduces new racing points that need to be handled, as well. Often, to deal with preemption, the simplest thing to do is to completely disable it. A critical section defines a piece of code (borderlined by the pair of functions man:critical_enter[9] and man:critical_exit[9], where preemption is guaranteed to not happen (until the protected code is fully executed). This can often replace a lock effectively but should be used carefully to not lose the whole advantage that preemption brings.
 
2 years ago
User avatar None

String updated in the repository

Documentation / articles/linux-emulation/_index — Persian

Scheduling barriers are intended to be used to drive scheduling of threading. They consist mainly of three different stubs:
 
2 years ago
Browse all translation changes