Searched full:call (Results 1 – 25 of 715) sorted by relevance
12345678910>>...29
| /Documentation/networking/ |
| D | rxrpc.txt | 63 (3) Retention of the reusable bits of the transport system set up for one call
122 (*) Each RxRPC operation is a "call". A connection may make up to four
147 explicitly sequenced per call.
158 (*) An call is complete when the request has been sent, the reply has been
162 (*) An call may be aborted by either end at any time up to its completion.
183 the last call currently using it has completed in case a new call is made
216 be used in all other sendmsgs or recvmsgs associated with that call. The
221 first sendmsg() of a call (struct msghdr::msg_name).
227 first sendmsg() of the call must specify the target address. The server's
230 (*) Once the application has received the last message associated with a call,
[all …]
|
| /Documentation/process/ |
| D | adding-syscalls.rst | 4 Adding a New System Call
7 This document describes what's involved in adding a new system call to the
12 System Call Alternatives
15 The first thing to consider when adding a new system call is whether one of
43 :manpage:`fcntl(2)` is a multiplexing system call that hides a lot of complexity, so
49 with :manpage:`fcntl(2)`, this system call is a complicated multiplexor so
57 A new system call forms part of the API of the kernel, and has to be supported
70 system call. To make sure that userspace programs can safely use flags
72 flags, and reject the system call (with ``EINVAL``) if it does::
109 If your new system call allows userspace to refer to a kernel object, it
[all …]
|
| /Documentation/crypto/ |
| D | userspace-if.rst | 23 and asynchronous invocations. The user space API call is fully
62 send()/write() system call family. The result of the cipher operation is
63 obtained with the read()/recv() system call family.
77 3. Invoke accept with the socket descriptor. The accept system call
88 the input buffer used for the send/write system call and the output
89 buffer used by the read/recv system call may be one and the same. This
120 Using the send() system call, the application provides the data that
121 should be processed with the message digest. The send system call allows
124 - MSG_MORE: If this flag is set, the send system call acts like a
126 calculated. If the flag is not set, the send system call calculates
[all …]
|
| /Documentation/userspace-api/ |
| D | seccomp_filter.rst | 13 surface exposed to the application. System call filtering is meant for
19 operated on is related to the system call being made: system call
20 number and the system call arguments. This allows for expressive
26 call interposition frameworks. BPF programs may not dereference
28 call arguments directly.
33 System call filtering isn't a sandbox. It provides a clearly defined
47 prctl(2) call as the strict seccomp. If the architecture has
54 reflecting the system call number, arguments, and other
65 call will return -1 and set errno to ``EINVAL``.
69 call ABI as the parent.
[all …]
|
| D | unshare.rst | 1 unshare system call
4 This document describes the new system call, unshare(). The document
39 call, applications can selectively choose which resources to share
42 unshare() system call adds a primitive to the Linux thread model that
98 changes to copy_* functions utilized by clone/fork system call.
108 unshare() reverses sharing that was done using clone(2) system call,
178 The unshare() call is Linux-specific and should not be used
187 Depending on the flags argument, the unshare() system call allocates
205 vm, if the system call encounters an error while allocating
208 system call will have to go back to older, shared, vm
[all …]
|
| /Documentation/arm/nwfpe/ |
| D | notes.rst | 10 registers f4-f7 to be preserved over a function call. The compiler quite
15 then made a function call. Upon return from the function call the number in
21 result from the function call and f4 were used in a multiplication. If the
31 moved to f4 to preserve it over the log(y) call. The division will be done
|
| /Documentation/media/uapi/dvb/ |
| D | video-fopen.rst | 73 This system call opens a named video device (e.g.
76 When an open() call has succeeded, the device will be ready for use. The
79 affect the semantics of the open() call itself. A device opened in
81 using the F_SETFL command of the fcntl system call. This is a standard
82 system call, documented in the Linux manual page for fcntl. Only one
86 ioctl call that can be used is VIDEO_GET_STATUS. All other call will
|
| D | audio-fopen.rst | 74 This system call opens a named audio device (e.g.
75 /dev/dvb/adapter0/audio0) for subsequent use. When an open() call has
79 of the open() call itself. A device opened in blocking mode can later be
81 of the fcntl system call. This is a standard system call, documented in
85 in O_RDONLY mode, the only ioctl call that can be used is
86 AUDIO_GET_STATUS. All other call will return with an error code.
|
| D | audio_data_types.rst | 21 The audio stream source is set through the AUDIO_SELECT_SOURCE call
36 through the ``write()`` system call.
41 The following values can be returned by the AUDIO_GET_STATUS call
73 The AUDIO_GET_STATUS call returns the following structure informing
92 The following structure is used by the AUDIO_SET_MIXER call to set the
109 A call to AUDIO_GET_CAPABILITIES returns an unsigned integer with the
|
| D | ca-fopen.rst | 59 This system call opens a named ca device (e.g. ``/dev/dvb/adapter?/ca?``)
62 When an ``open()`` call has succeeded, the device will be ready for use. The
65 affect the semantics of the ``open()`` call itself. A device opened in
67 using the ``F_SETFL`` command of the ``fcntl`` system call. This is a
68 standard system call, documented in the Linux manual page for fcntl.
|
| D | video-freeze.rst | 42 - File descriptor returned by a previous call to open().
57 This ioctl call suspends the live video stream being played. Decoding
60 If VIDEO_SOURCE_MEMORY is selected in the ioctl call
62 until the ioctl call VIDEO_CONTINUE or VIDEO_PLAY is performed.
|
| D | video-get-event.rst | 42 - File descriptor returned by a previous call to open().
63 This ioctl call returns an event of type video_event if available. If
65 in blocking or non-blocking mode. In the latter case, the call fails
66 immediately with errno set to ``EWOULDBLOCK``. In the former case, the call
72 for this ioctl call.
|
| D | video_types.rst | 48 VIDEO_SET_DISPLAY_FORMAT call (??) which accepts
67 The video stream source is set through the VIDEO_SELECT_SOURCE call
78 system call */
84 through the **write()** system call.
92 The following values can be returned by the VIDEO_GET_STATUS call
162 VIDEO_GET_EVENT call.
187 The VIDEO_GET_STATUS call returns the following structure informing
218 An I-frame displayed via the VIDEO_STILLPICTURE call is passed on
236 A call to VIDEO_GET_CAPABILITIES returns an unsigned integer with the
|
| /Documentation/infiniband/ |
| D | core_locking.rst | 41 are therefore safe to call from any context.
48 the midlayer is also safe to call from any context.
64 example, a consumer may safely call ib_poll_cq() on multiple CPUs
72 same callchain as an ib_device method call. For example, it is not
73 allowed for a low-level driver to call a consumer's completion event
105 must be complete before this call. The device must remain usable
106 until the driver's call to ib_unregister_device() has returned.
108 A low-level driver must call ib_register_device() and
|
| /Documentation/filesystems/ |
| D | autofs-mount-control.txt | 155 the number of times to call the expire ioctl. This involves scanning
159 issued for a mount (file handle) we should continually call back to
201 point. It is returned by the open call and is used by all calls except
215 the void function call init_autofs_dev_ioctl(struct autofs_dev_ioctl *).
258 by loaded module. This call requires an initialized struct autofs_dev_ioctl
269 path. The open call requires an initialized struct autofs_dev_ioctl with
273 shown in /proc/mounts. The close call requires an initialized struct
275 from the open call. The release of the file descriptor can also be done
277 The close call is included in the implemented operations largely for
287 call and the token field of struct args_ready or struct args_fail set
[all …]
|
| D | journalling.rst | 13 resides. The :c:func:`jbd2_journal_init_inode` call is for journals stored in
14 filesystem inodes, or the :c:func:`jbd2_journal_init_dev` call can be used
17 finished make sure you call :c:func:`jbd2_journal_destroy` on it to free up
23 When loading the journal you must call :c:func:`jbd2_journal_load` to process
26 may call :c:func:`jbd2_journal_wipe` to clear the journal contents before
32 call :c:func:`jbd2_journal_recover` if necessary. I would advise reading
46 reenter a transaction if necessary, but remember you must call
54 need to call :c:func:`jbd2_journal_get_create_access()` /
60 buffer, and once you are have done so you need to call
63 device you can call :c:func:`jbd2_journal_forget` in much the same way as you
[all …]
|
| /Documentation/trace/ |
| D | ftrace-design.rst | 39 The exact mcount symbol name will depend on your toolchain. Some call it
44 call mcount
54 mcount call (before/after function prologue). You might also want to look at
60 so return immediately. If it isn't, then call that function in the same way
63 size of the mcount call that is embedded in the function).
126 function, call the arch-specific function ftrace_graph_caller which in turn
137 That function will simply call the common ftrace_return_to_handler function and
139 original call site.
218 Similarly, when you call ftrace_return_to_handler(), pass it the frame pointer.
251 - If the system call table on this arch is more complicated than a simple array
[all …]
|
| /Documentation/driver-api/serial/ |
| D | driver.rst | 81 This call must not sleep
102 This call must not sleep
123 This call must not sleep
137 This call must not sleep
146 This call must not sleep
171 will append the character to the circular buffer and then call
188 This call must not sleep
201 This call must not sleep
206 should be terminated when another call is made with a zero
214 RTS nor DTR; this will be done via a separate call to set_mctrl.
[all …]
|
| /Documentation/ia64/ |
| D | fsys.rst | 13 execution to the ia64 linux kernel. We call this mode the
82 (fsyscall_table). This table contains one entry for each system call.
83 By default, a system call is handled by fsys_fallback_syscall(). This
85 normal Linux system call handler. For performance-critical system
88 of the getpid() system call.
98 r15 system call number
100 r32-r39 system call arguments
112 r15 system call number (as passed into the fsyscall handler)
113 r32-r39 system call arguments (as passed into the fsyscall handler)
124 doing a full system call (by calling fsys_fallback_syscall).
[all …]
|
| /Documentation/power/ |
| D | userland-swsusp.rst | 47 the value of which will indicate whether the call returned after
58 operation; this call will not succeed if the snapshot
76 contain the result if the call is successful).
81 will contain the swap page offset if the call is successful)
106 suspend to RAM; using this call causes the kernel to
107 immediately enter the suspend-to-RAM state, so this call must always
108 be preceded by the SNAPSHOT_FREEZE call and it is also necessary
109 to use the SNAPSHOT_UNFREEZE call after the system wakes up. This call
121 a page in the previous call, you will only be able to read()
122 **at most** 1/2 of the page in the next call)
|
| /Documentation/filesystems/nfs/ |
| D | idmapper.txt | 8 ways NFS could obtain this information: placing a call to /sbin/request-key
9 or by placing a call to the rpc.idmap daemon.
11 NFS will attempt to call /sbin/request-key first. If this succeeds, the
12 result will be cached using the generic request-key cache. This call should
17 If the call to /sbin/request-key fails (if /etc/request-key.conf is not
71 determines the correct function to call by looking at the first part of the
|
| /Documentation/scheduler/ |
| D | sched-arch.rst | 15 To request the scheduler call switch_to with the runqueue unlocked,
27 be enabled to call schedule() then disabled again.
34 3. When cpu_idle finds (need_resched() == 'true'), it should call
35 schedule(). It should not call schedule() otherwise.
71 ia64 - is safe_halt call racy vs interrupts? (does it sleep?) (See #4a)
|
| /Documentation/virt/ |
| D | paravirt_ops.rst | 23 - simple indirect call
25 known that the overhead of indirect call isn't very important.
27 - indirect call which allows optimization with binary patch
|
| /Documentation/ |
| D | padata.txt | 132 exactly one call to the above-mentioned parallel() function, on one CPU, so
141 need not be completed during this call, but, if parallel() leaves work
145 fact with a call to::
149 At some point in the future, padata_do_serial() will trigger a call to the
150 serial() function in the padata_priv structure. That call will happen on
151 the CPU requested in the initial call to padata_do_parallel(); it, too, is
153 Note that this call may be deferred for a while since the padata code takes
163 might be best not to call it while there is work outstanding.
|
| D | xz.txt | 11 compression ratio even further. E.g. Branch/Call/Jump (BCJ) filters
28 The xz_dec module provides XZ decompressor with single-call (buffer
29 to buffer) and multi-call (stateful) APIs. The usage of the xz_dec
49 $(call if_needed). The kernel image should be compressed with
50 $(call if_needed,xzkern) which will use a BCJ filter and a big LZMA2
53 Other things should be compressed with $(call if_needed,xzmisc)
84 is used in single-call mode. Decompressing the kernel itself is an
85 example of this situation. In single-call mode, the memory usage
|
12345678910>>...29