这显然会改进性能，因为不需要通过系统调用请求更多内存。
This obviously improves performance, because you don't need to go through system calls to request additional memory.
好像不存在收集参数信息(比如内存堆的使用)的直接的系统调用。
Direct system calls to gather information about parameters (like memory heap usage) don't seem to exist.
内存和用户数量对系统调用的影响
这个系统调用需要shm_open返回的文件描述符，它返回指向内存的指针。
This system call requires the file descriptor from shm_open and returns a pointer to memory.
如果你允许WLocker调用主屏幕，WidgetLocker会将自己在系统内存中设为高优先级，让它像正常的锁定屏幕一样立刻弹出。
If you allow WLocker to call for Home, it keeps WidgetLocker itself running with high priority in the system memory, making it popup instantly like a regular lock screen would.
但是如果堆的空间不能满足程序的内存申请，那么brk函数会执行系统调用(implementation)来增加堆的内存空间以满足程序的请求。
Otherwise the heap is enlarged via the BRK system call (implementation) to make room for the requested block.
用特殊的系统调用(即对UNIX内核的请求)分配和释放内存并设置权限；通过一般的读写操作读写内存段中的数据。
Special system calls, or requests to the UNIX kernel, allocate and free the memory and set permissions; common read and write operations put and get data from the region.
此时write系统调用会被进程接收到的SIGBUS信号中断，因为当前进程访问了非法内存地址。
Your write system call will be interrupted by the bus error signal SIGBUS, because you performed a bad memory access.
因为它在边界处，它是唯一一个可以任意的扩展（通过Unix的sbrk系统调用）成更大的块（除非因为所有的内存已经被消耗光了导致sbrk失败）。
Because it is at the border, it is the only chunk that can be arbitrarily extended (via sbrk in Unix) to be bigger than it is (unless of course sbrk fails because all memory has been exhausted).
清单5 - 4演示了一个用于分配内核内存的系统调用。
Listing 5-4 shows a system call module designed to allocate kernel memory.
这个系统调用要求两个参数：一个包含要分配内存数量的长整数，还有一个存储返回的地址的长整数指针。
The system call is invoked with two arguments: a long integer containing the amount of memory to allocate and a long integer pointer to store the returned address.
因此，一个有动态内存需求的进程需要发出系统调用(请求内存和释放内存)通知操作系统它的这一内存变化需要。
Thus, a process with dynamic memory requirements will need to issue system calls (request memory and release memory) to inform the operating system of its changing memory needs.
获取操作系统调用的、启动此线程的函数的内存地址。
Gets the memory address of the function that the operating system called that started this thread.
研究了在微处理器PXA255上实现内存管理、进程调度、中断处理和系统调用的机制。
The research on microprocessor PXA255 includes realization of EMS memory, process scheduling, interrupt disposal and system call mechanism.
通常不需要再次调用除非视图被隐藏和系统回收内存，持有其像素。
Often it doesn't need to be called again at all unless the view is hidden and the OS recycled the memory that was holding its pixels.
它可能会因未调用构造函数而使用未初始化的内存而导致随机行为或系统崩溃。
It might cause random behavior or crashes due to usage of uninitialized memory because constructors are not invoked.
它可能会因未调用构造函数而使用未初始化的内存而导致随机行为或系统崩溃。
It might cause random behavior or crashes due to usage of uninitialized memory because constructors are not invoked.
应用推荐