Searched full:call (Results 1 – 25 of 826) sorted by relevance
12345678910>>...34
| /Documentation/networking/ |
| D | rxrpc.rst | 64 (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.
182 the last call currently using it has completed in case a new call is made
215 be used in all other sendmsgs or recvmsgs associated with that call. The
220 first sendmsg() of a call (struct msghdr::msg_name).
226 first sendmsg() of the call must specify the target address. The server's
229 (#) 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/staging/ |
| D | xz.rst | 12 the LZMA2 filter and optionally also 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 in include/linux/xz.h.
37 ``$(call if_changed)``. They require the xz tool from XZ Utils.
39 - ``$(call if_changed,xzkern)`` is for compressing the kernel image.
43 - ``$(call if_changed,xzkern_with_size)`` is like ``xzkern`` above but
47 - Other things can be compressed with ``$(call if_needed,xzmisc)``
71 - In multi-call mode the dictionary is allocated as part of the
77 - In single-call mode the output buffer is used as the dictionary
82 as big as the uncompressed data. A notable example of single-call
|
| /Documentation/arch/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/driver-api/ |
| D | wbrf.rst | 59 1. During probe, call `acpi_amd_wbrf_supported_producer` to check if WBRF
61 2. On using some frequency band, call `acpi_amd_wbrf_add_remove` with 'add'
63 3. Or on stopping using some frequency band, call
67 1. During probe, call `acpi_amd_wbrf_supported_consumer` to check if WBRF
69 2. Call `amd_wbrf_register_notifier` to register for notification
71 3. Call the `amd_wbrf_retrieve_freq_band` initially to retrieve
77 5. During driver cleanup, call `amd_wbrf_unregister_notifier` to
|
| /Documentation/userspace-api/media/dvb/ |
| D | legacy_dvb_video.rst | 137 `VIDEO_SET_DISPLAY_FORMAT`_ call which accepts this enum as argument.
224 system call.
229 The video stream source is set through the `VIDEO_SELECT_SOURCE`_ call
235 through the `write()`_ system call.
283 This values can be returned by the `VIDEO_GET_STATUS`_ call
608 `VIDEO_GET_EVENT`_ call. See there for more details.
620 The `VIDEO_GET_STATUS`_ call returns the following structure informing
736 An I-frame displayed via the `VIDEO_STILLPICTURE`_ call is passed on
797 A call to `VIDEO_GET_CAPABILITIES`_ returns an unsigned integer with the
831 - :cspan:`1` File descriptor returned by a previous call
[all …]
|
| D | legacy_dvb_audio.rst | 72 the `write()`_ system call.
77 The audio stream source is set through the `AUDIO_SELECT_SOURCE`_ call
132 This values can be returned by the `AUDIO_GET_STATUS`_ call
243 This structure is used by the `AUDIO_SET_MIXER`_ call to set the
353 The `AUDIO_GET_STATUS`_ call returns this structure as information
446 A call to `AUDIO_GET_CAPABILITIES`_ returns an unsigned integer with the
480 - File descriptor returned by a previous call to `open()`_.
494 This ioctl call asks the Audio Device to stop playing the current
531 - File descriptor returned by a previous call to `open()`_.
545 This ioctl call asks the Audio Device to start playing an audio stream
[all …]
|
| D | ca-fopen.rst | 49 This system call opens a named ca device (e.g. ``/dev/dvb/adapter?/ca?``)
52 When an ``open()`` call has succeeded, the device will be ready for use. The
55 affect the semantics of the ``open()`` call itself. A device opened in
57 using the ``F_SETFL`` command of the ``fcntl`` system call. This is a
58 standard system call, documented in the Linux manual page for fcntl.
|
| D | dmx-fclose.rst | 24 File descriptor returned by a previous call to
30 This system call deactivates and deallocates a filter that was
31 previously allocated via the :c:func:`open()` call.
|
| D | fe-diseqc-reset-overload.rst | 32 this ioctl call restores the power to the bus. The call requires
33 read/write access to the device. This call has no effect if the device
|
| /Documentation/infiniband/ |
| D | core_locking.rst | 39 are therefore safe to call from any context.
46 the midlayer is also safe to call from any context.
62 example, a consumer may safely call ib_poll_cq() on multiple CPUs
70 same callchain as an ib_device method call. For example, it is not
71 allowed for a low-level driver to call a consumer's completion event
103 must be complete before this call. The device must remain usable
104 until the driver's call to ib_unregister_device() has returned.
106 A low-level driver must call ib_register_device() and
|
| /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.
231 - If the system call table on this arch is more complicated than a simple array
[all …]
|
| D | ftrace-uses.rst | 58 To enable tracing call::
62 To disable tracing call::
98 the function being traced (where the call of the function occurred).
115 called by a callback may also be traced, and call that same callback,
145 function call.
161 function call.
188 protection and only call the callback if it did not recurse.
264 To add more functions, call the ftrace_set_filter() more than once with the
282 Although the ip must be the address where the call to fentry or mcount is
314 functions should call the callback, it is best to set the filters before
[all …]
|
| /Documentation/filesystems/ |
| D | autofs-mount-control.rst | 157 the number of times to call the expire ioctl. This involves scanning
161 issued for a mount (file handle) we should continually call back to
203 point. It is returned by the open call and is used by all calls except
217 the void function call init_autofs_dev_ioctl(``struct autofs_dev_ioctl *``).
260 by loaded module. This call requires an initialized struct autofs_dev_ioctl
271 path. The open call requires an initialized struct autofs_dev_ioctl with
275 shown in /proc/mounts. The close call requires an initialized struct
277 from the open call. The release of the file descriptor can also be done
279 The close call is included in the implemented operations largely for
289 call and the token field of struct args_ready or struct args_fail set
[all …]
|
| D | journalling.rst | 13 resides. The jbd2_journal_init_inode() call is for journals stored in
14 filesystem inodes, or the jbd2_journal_init_dev() call can be used
17 finished make sure you call jbd2_journal_destroy() on it to free up
23 When loading the journal you must call jbd2_journal_load() to process
26 may call jbd2_journal_wipe() to clear the journal contents before
32 call jbd2_journal_recover() if necessary. I would advise reading
46 reenter a transaction if necessary, but remember you must call
54 need to call jbd2_journal_get_create_access() /
60 buffer, and once you are have done so you need to call
63 device you can call jbd2_journal_forget() in much the same way as you
[all …]
|
| D | coda.rst | 49 4. The interface at the call level
141 a process P which accessing a Coda file. It makes a system call which
166 come back to the FS driver, servicing of the VFS call continues and
242 call. This action finishes in the kernel by putting the message on the
244 passed the contents of the data buffer. The getmsg_from_kernel call
255 mode context of Venus) and the sendmsg_to_kernel call returns to
269 sendmsg_to_kernel call. In the normal case, the upcall routine will
296 with a write and notification is through the select system call on the
301 call is used. The DeviceIoControl call is designed to copy buffers
303 is issued as a synchronous call, while the getmsg_from_kernel call is
[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
73 will contain the result if the call is successful)
78 will contain the result if the call is successful)
83 will contain the swap page offset if the call is successful)
108 suspend to RAM; using this call causes the kernel to
109 immediately enter the suspend-to-RAM state, so this call must always
110 be preceded by the SNAPSHOT_FREEZE call and it is also necessary
111 to use the SNAPSHOT_UNFREEZE call after the system wakes up. This call
123 a page in the previous call, you will only be able to read()
[all …]
|
| /Documentation/core-api/ |
| D | padata.rst | 115 exactly one call to the above-mentioned parallel() function, on one CPU, so
124 need not be completed during this call, but, if parallel() leaves work
132 the work) should inform padata of the fact with a call to::
136 At some point in the future, padata_do_serial() will trigger a call to the
137 serial() function in the padata_priv structure. That call will happen on
138 the CPU requested in the initial call to padata_do_parallel(); it, too, is
140 Note that this call may be deferred for a while since the padata code takes
162 piece of the job that one thread completes in one call to the thread function.
167 call each time it assigns a job chunk to a thread. Then, define the thread
171 typically allocated on the main thread's stack. Last, call
|
| /Documentation/translations/zh_CN/staging/ |
| D | xz.rst | 19 压缩率的Branch/Call/Jump (BCJ)过滤器。
46 在内核的makefiles中，提供了使用$(call if_needed)的两个命令。内核镜像应该
47 使用$(call if_needed,xzkern)来压缩，它会使用BCJ过滤器和一个大LZMA2字典。
49 应该使用$(call if_needed,xzmisc)来压缩，它会使用1 MiB的LZMA2字典并禁用
|
| /Documentation/admin-guide/nfs/ |
| D | nfs-idmapper.rst | 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
74 determines the correct function to call by looking at the first part of the
|
| /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/ABI/testing/ |
| D | dell-smbios-wmi | 12 1) To perform an SMBIOS call from userspace, you'll need to
30 call you're interested in. Typically SMBIOS buffers have
37 6) Run the call by using ioctl() as described in the header.
|
12345678910>>...34