针对这个新函数更新系统调用表。
这个系统调用返回一个文件描述符。
使用新的内核系统调用有两种方法。
There are two ways that you can use new kernel system calls.
为此它使用了系统调用fork 。
UNIX系统调用的具体细节。
这就是第3个步骤，更新系统调用表。
SCI的核心是系统调用多路分解表。
At the core of the SCI is the system call demultiplexing table.
在库中封装网络通信所需的系统调用。
Encapsulation of the systems calls in a library that are necessary to communicate over the network.
在bind系统调用函数中。
本文仅讨论sendmsg系统调用。
使用exec系列系统调用。
您还需要考虑系统调用跟踪本身的开销。
系统调用接口可以从两个角度进行描述。
The system call interface can be described from two perspectives.
TAMOS内核扩展拦截所有系统调用。
清单1.madvise系统调用。
系统调用功能的验证测试。
当前，对于系统调用，只支持出口探查点。
Currently, the exit probe point is supported for system calls only.
套接字层接收进行的任何TCP系统调用。
Any TCP system call that is made is received by the socket layer.
清单3. sendfile系统调用。
系统调用是模拟中最简单也是最困难的部分。
System calls are the easiest and the hardest part of emulation.
系统调用是请求内核中服务的一种有效方法。
System calls are an efficient way of requesting services in the kernel.
通常，这种调用通过系统调用接口间接完成。
Most frequently, such calls are made indirectly, though a system call interface.
任何后续的系统调用都使用创建的套接字标识。
Any subsequent system calls are identified with the created socket.
这个系统调用向指定设备发送控制代码和其他数据。
This system call sends control code and other data to a specified device.
就调用方式而言，系统调用与库函数之间没有区别。
In terms of the way it is called, there is no difference between a system call and a library function.
您可以将它们作为程序员友好的接口来进行系统调用。
You can think of them as a programmer-friendly interface to system calls.
每个系统调用都是通过一个单一的入口点多路传入内核。
Each system call is multiplexed into the kernel through a single entry point.
这些步骤包含了内核所提供的更小的构件，即系统调用。
These steps involve smaller building blocks that the kernel provides, which are the system calls.
困难之处在于可能难以或者不可能较好地实现系统调用。
The hard part is that the system call may be difficult or impossible to implement reasonably.
争用同步之所以慢，是因为它涉及多个线程切换和系统调用。
Contended synchronizations are slow because they involve multiple thread switches and system calls.
应用推荐