JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... ムでスレッド用のスタックを手動で割り当てている。 この場合には、guard size 属性は無視される。 $ ./a.out -g 4096 -s 0x8000 -a Allocated thread stack at 0x804d000 Thread attributes object after initializations: Guard size = 4096 bytes Stack address = 0x804d0 ... printf(stderr, "Usage: %s [-s stack-size [-a]]" " [-g guard-size]\n", pname); fprintf(stderr, "\t\t-a means program should allocate stack\n"); exit(EXIT_FAILURE); } static pthread_attr_t * /* Get thread attributes from command line */ get_thread_attribut ... es_from_cl(int argc, char *argv[], pthread_attr_t *attrp) { int s, opt, allocate_stack; size_t stack_size, guard_size; void *stack_addr; pthread_attr_t *ret_attrp = NULL; /* Set to attrp if we initialize ... ... 同様に) 「ローカルからの割り当て」となる。 MPOL_LOCAL (Linux 3.8 以降) This mode specifies "local allocation"; the memory is allocated on the node of the CPU that triggered the allocation (the "local node"). The nodemask and maxnode arguments must specify ... the empty set. If the "local node" is low on free memory, the kernel will try to allocate memory from other nodes. The kernel will allocate memory from the "local node" whenever memory for this node is available. ... If the "local node" is not allowed by the process's current cpuset context, the kernel will try to allocate memory from other nodes. The kernel will allocate memory from the "local node" whenever it becomes allowed by the process' ... ... from the node with sufficient free memory that is closest to the node where the allocation takes place. Pages will not be allocated from any node not specified in the IR nodemask . (Before Linux 2.6.26, page allocations came from the node with the lowes ... のノードに メモリー割り当てが行われる。 MPOL_LOCAL (Linux 3.8 以降) This mode specifies "local allocation"; the memory is allocated on the node of the CPU that triggered the allocation (the "local node"). The nodemask and maxnode arguments must specify ... the empty set. If the "local node" is low on free memory, the kernel will try to allocate memory from other nodes. The kernel will allocate memory from the "local node" whenever memory for this node is available. ... ... was exhausted while synchronizing. ENOSPC , EDQUOT Data was written to a files on NFS or another filesystem which does not allocate space at the time of a write (2) system call, and some previous write failed due to insufficient storage space. バージョン ... ... was exhausted while synchronizing. ENOSPC , EDQUOT Data was written to a files on NFS or another filesystem which does not allocate space at the time of a write (2) system call, and some previous write failed due to insufficient storage space. バージョン ... ... 値が RLIMIT_NOFILE を超えた。 EINVAL ( ppoll ()) The timeout value expressed in *ip is invalid (negative). ENOMEM Unable to allocate memory for kernel data structures. バージョン poll () システムコールは Linux 2.1.23 で導入された。このシステムコールが存在 ... affected by the O_NONBLOCK flag. On some other UNIX systems, poll () can fail with the error EAGAIN if the system fails to allocate kernel-internal resources, rather than ENOMEM as Linux does. POSIX permits this behavior. Portable programs may wish to ch ... ... 値が RLIMIT_NOFILE を超えた。 EINVAL ( ppoll ()) The timeout value expressed in *ip is invalid (negative). ENOMEM Unable to allocate memory for kernel data structures. バージョン poll () システムコールは Linux 2.1.23 で導入された。このシステムコールが存在 ... affected by the O_NONBLOCK flag. On some other UNIX systems, poll () can fail with the error EAGAIN if the system fails to allocate kernel-internal resources, rather than ENOMEM as Linux does. POSIX permits this behavior. Portable programs may wish to ch ... ... イプ、FIFO、ソケットなど) を参照している。 ENOSPC , EDQUOT fd is bound to a file on NFS or another filesystem which does not allocate space at the time of a write (2) system call, and some previous write failed due to insufficient storage space. 準拠 POSIX ... ... イプ、FIFO、ソケットなど) を参照している。 ENOSPC , EDQUOT fd is bound to a file on NFS or another filesystem which does not allocate space at the time of a write (2) system call, and some previous write failed due to insufficient storage space. 準拠 POSIX ... ... [out] */ unsigned char f_handle[0]; /* File identifier (sized by caller) [out] */ }; It is the caller's responsibility to allocate the structure with a size large enough to hold the handle returned in f_handle . Before the call, the handle_bytes field s ... hould be initialized to contain the allocated size for f_handle . (The constant MAX_HANDLE_SZ , defined in < fcntl.h > , specifies the maximum expected size for a file ... error EOVERFLOW and handle->handle_bytes is set to indicate the required size; the caller can then use this information to allocate a structure of the correct size (see EXAMPLES below). Some care is needed here as EOVERFLOW can also indicate that no file ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。