| /Linux-v5.10/Documentation/networking/ |
| D | msg_zerocopy.rst | 23 notification overhead. As a result, MSG_ZEROCOPY is generally only
33 The kernel returns a notification when it is safe to modify data.
106 The notification itself is a simple scalar value. Each socket
114 Notification Reception
148 Notification Batching
156 When a new notification is about to be queued, it checks whether the
157 new value extends the range of the notification at the tail of the
158 queue. If so, it drops the new notification packet and instead increases
159 the range upper value of the outstanding notification.
162 notification can be squashed into the previous one, so that no more
[all …]
|
| /Linux-v5.10/Documentation/ |
| D | watch_queue.rst | 2 General notification mechanism
5 The general notification mechanism is built on top of the standard pipe driver
6 whereby it effectively splices notification messages from the kernel into pipes
14 "General setup"/"General notification queue"
29 additions to the ring - which might end up interleaved with notification
45 Note that when producing a notification, the kernel does not wait for the
54 Notification messages begin with a short header::
62 "type" indicates the source of the notification record and "subtype" indicates
85 notification producer to indicate some meaning specific to the type and
94 Watch List (Notification Source) API
[all …]
|
| /Linux-v5.10/drivers/net/wimax/i2400m/ |
| D | usb-notif.c | 3 * Notification handling
41 * The notification endpoint is active when the device is not in boot
72 * Process a received notification
75 * on the notification endpoint:
114 * URB callback for the notification endpoint
116 * @urb: the urb received from the notification endpoint
152 dev_err(dev, "notification: URB error %d, retrying\n", in i2400mu_notification_cb()
166 dev_err(dev, "notification: cannot submit URB: %d\n", ret); in i2400mu_notification_cb()
174 dev_err(dev, "maximum errors in notification URB exceeded; " in i2400mu_notification_cb()
185 * setup the notification endpoint
[all …]
|
| /Linux-v5.10/drivers/soc/fsl/dpio/ |
| D | dpio.h | 22 * enum dpio_channel_mode - DPIO notification channel mode
23 * @DPIO_NO_CHANNEL: No support for notification channel
35 * @channel_mode: Notification channel mode
36 * @num_priorities: Number of priorities for the notification channel (1-8);
58 * @channel_mode: Notification channel mode
59 * @num_priorities: Number of priorities for the notification channel (1-8);
|
| /Linux-v5.10/include/uapi/linux/ |
| D | watch_queue.h | 9 #define O_NOTIFICATION_PIPE O_EXCL /* Parameter to pipe2() selecting notification pipe */
16 WATCH_TYPE_KEY_NOTIFY = 1, /* Key change event notification */
26 * Notification record header. This is aligned to 64-bits so that subclasses
50 * Notification filtering rules (IOC_WATCH_QUEUE_SET_FILTER).
67 * Extended watch removal notification. This is used optionally if the type
80 * Type of key/keyring change notification.
94 * Key/keyring notification record.
|
| D | mqueue.h | 44 * If the notification is triggered, then the cookie is sent to the netlink
46 * NOTIFY_WOKENUP if the notification got triggered, NOTIFY_REMOVED if it was
48 * mq_notify() that removed the notification.
|
| /Linux-v5.10/include/uapi/xen/ |
| D | gntalloc.h | 54 * Sets up an unmap notification within the page, so that the other side can do
56 * mutexes or close notification on communication channels.
58 * Each mapped page only supports one notification; multiple calls referring to
59 * the same page overwrite the previous notification. You must clear the
60 * notification prior to the IOCTL_GNTALLOC_DEALLOC_GREF if you do not want it
70 * notification we are adjusting.
|
| /Linux-v5.10/drivers/firmware/arm_scmi/ |
| D | notify.h | 4 * notification header file containing some definitions, structures
5 * and function prototypes related to SCMI Notification handling.
21 * @max_payld_sz: Max possible size for the payload of a notification message
22 * @max_report_sz: Max possible size for the report of a notification message
35 * struct scmi_event_ops - Protocol helpers called by the notification core.
|
| D | notify.c | 3 * System Control and Management Interface (SCMI) Notification support
11 * interested agents via notification messages: this is an implementation
15 * An SCMI Notification core instance is initialized for each active platform
25 * events' delivery using the standard Kernel notification chains machinery.
28 * of the SCMI Protocol itself, the underlying notification chains are created
36 * All users provided callbacks and allocated notification-chains are stored in
42 * and is served by its own dedicated notification chain; information contained
51 * Upon reception of a notification message from the platform the SCMI RX ISR
59 * queued items into the proper notification-chain: notifications processing can
64 * Events' information is then extracted from the SCMI Notification messages and
[all …]
|
| /Linux-v5.10/Documentation/power/ |
| D | pm_qos_interface.rst | 40 value and recompute the new aggregated target, calling the notification tree
45 and call the notification tree if the target was changed as a result of
56 Adds a notification callback function to the CPU latency QoS. The callback is
60 Removes the notification callback function from the CPU latency QoS.
115 value and recompute the new aggregated target, calling the notification
120 and call the notification trees if the target was changed as a result of
166 Notification mechanisms:
168 The per-device PM QoS framework has a per-device notification tree.
171 Adds a notification callback function for the device for a particular request
178 Removes the notification callback function for the device.
|
| /Linux-v5.10/net/sctp/ |
| D | ulpevent.c | 109 * provided by this notification.
128 * head room to use as notification. in sctp_ulpevent_make_assoc_change()
140 /* Include the notification structure */ in sctp_ulpevent_make_assoc_change()
186 * This field is the total length of the notification data, including in sctp_ulpevent_make_assoc_change()
187 * the notification header. in sctp_ulpevent_make_assoc_change()
272 * This field is the total length of the notification data, including in sctp_ulpevent_make_peer_addr_change()
273 * the notification header. in sctp_ulpevent_make_peer_addr_change()
358 /* Create and initialize an SCTP_REMOTE_ERROR notification.
393 * notification with. in sctp_ulpevent_make_remote_error()
425 /* Create and initialize a SCTP_SEND_FAILED notification.
[all …]
|
| /Linux-v5.10/Documentation/firmware-guide/acpi/ |
| D | acpi-lid.rst | 32 the lid state upon the last lid notification instead of returning the lid
43 changed to "opened". Thus the "opened" notification is not guaranteed. But
45 state is changed to "closed". The "closed" notification is normally used to
71 events and the unreliable initial state notification, Linux users can use
82 notification is missing.
93 control method is not reliable and the initial lid state notification is
97 and the unreliable initial state notification, Linux users should always
|
| /Linux-v5.10/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| D | time-event.h | 142 * @TE_V1_NOTIF_HOST_EVENT_START: request/receive notification on event start
143 * @TE_V1_NOTIF_HOST_EVENT_END:request/receive notification on event end
146 * @TE_V1_NOTIF_HOST_FRAG_START: request/receive notification on frag start
147 * @TE_V1_NOTIF_HOST_FRAG_END:request/receive notification on frag end
152 * A notification (both event and fragment) includes a status indicating weather
154 * notification the status is always success. There is no start/end fragment
155 * notification for monolithic events.
202 * A notification (both event and fragment) includes a status indicating weather
204 * notification the status is always success. There is no start/end fragment
205 * notification for monolithic events.
[all …]
|
| /Linux-v5.10/Documentation/ABI/stable/ |
| D | thermal-notification | 1 What: A notification mechanism for thermal related events
3 This interface enables notification for thermal related events.
4 The notification is in the form of a netlink event.
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | dnotify.rst | 4 Linux Directory Notification
9 The intention of directory notification is to allow user applications
11 The basic mechanism involves the application registering for notification
28 Usually, the application must reregister after each notification, but
46 The notification should work for any local access to files even if the
|
| /Linux-v5.10/fs/notify/ |
| D | notification.c | 7 * Basic idea behind the notification queue: An fsnotify group (like inotify)
8 * sends the userspace notification about events asynchronously some time after
11 * multiple group's notification queues we can't add the event directly to each
14 * going to end up on one, and only one, notification queue we embed one
78 * Add an event to the group notification queue. The group can later pull this
144 * Remove and return the first event from the notification list. It is the
|
| /Linux-v5.10/arch/x86/kvm/vmx/ |
| D | posted_intr.h | 13 /* bit 256 - Outstanding Notification */
15 /* bit 257 - Suppress Notification */
19 /* bit 279:272 - Notification Vector */
23 /* bit 319:288 - Notification Destination */
|
| /Linux-v5.10/drivers/misc/vmw_vmci/ |
| D | vmci_doorbell.c | 30 * DoorbellEntry describes the a doorbell notification handle allocated by the
69 * the case where multiple handles share a notification index, we hand out
147 * Below we try to allocate an index in the notification in dbell_index_table_add()
207 * notification index, we take the opportunity to in dbell_index_table_remove()
226 * index in the bitmap in the device backend. A notification state
245 * the device backend. The notification state is destroyed in hypervisor.
262 * host via the hypervisor with the notification info.
290 * Dispatches a doorbell notification to the host context.
324 * Register the notification bitmap with the host.
343 pr_devel("Failed to register (PPN=%llu) as notification bitmap (error=%d)\n", in vmci_dbell_register_notification_bitmap()
[all …]
|
| /Linux-v5.10/drivers/pci/hotplug/ |
| D | acpiphp_ibm.c | 74 /* struct notification - keeps info about the device
75 * that cause the ACPI notification event
77 struct notification { struct
95 static struct notification ibm_note; argument
237 * @context: passed context (our notification struct)
249 * has returned, thereby enforcing serial access for the notification struct.
255 struct notification *note = context; in ibm_handle_events()
257 pr_debug("%s: Received notification %02x\n", __func__, event); in ibm_handle_events()
451 pr_err("%s: Failed to register notification handler\n", in ibm_acpiphp_init()
483 pr_err("%s: Notification handler removal failed\n", __func__); in ibm_acpiphp_exit()
|
| /Linux-v5.10/drivers/w1/ |
| D | w1_netlink.h | 28 * @W1_SLAVE_ADD: notification that a slave device was added
29 * @W1_SLAVE_REMOVE: notification that a slave device was removed
30 * @W1_MASTER_ADD: notification that a new bus master was added
31 * @W1_MASTER_REMOVE: notification that a bus masterwas removed
|
| /Linux-v5.10/include/linux/ |
| D | fsnotify_backend.h | 3 * Filesystem access notification for Linux
173 * A group is a "thing" that wants to receive notification about filesystem
191 /* needed to send notification to userspace */
194 wait_queue_head_t notification_waitq; /* read() on the notification file blocks on this waitq */
216 struct fasync_struct *fsn_fa; /* async notification */
219 * notification list is too
485 /* attach the event to the group notification queue */
490 /* Queue overflow event to a notification group */
496 /* true if the group notification queue is empty */
498 /* return, but do not dequeue the first event on the notification queue */
[all …]
|
| /Linux-v5.10/Documentation/core-api/ |
| D | memory-hotplug.rst | 10 Hotplugging events are sent to a notification queue.
12 There are six types of notification defined in ``include/linux/memory.h``:
85 further processing of the notification queue.
87 NOTIFY_STOP stops further processing of the notification queue.
|
| /Linux-v5.10/drivers/dma/fsl-dpaa2-qdma/ |
| D | dpaa2-qdma.h | 47 #define QDMA_SER_DISABLE (8) /* no notification */
48 #define QDMA_SER_CTX BIT(8) /* notification by FQD_CTX[fqid] */
49 #define QDMA_SER_DEST (2 << 8) /* notification by destination desc */
50 #define QDMA_SER_BOTH (3 << 8) /* soruce and dest notification */
|
| /Linux-v5.10/Documentation/hwmon/ |
| D | acpi_power_meter.rst | 32 socket and a poll notification will be sent to the appropriate
42 the netlink event socket and a poll notification will be sent to the
49 well as sent as a poll notification to a sysfs file. The events are as
|
| /Linux-v5.10/drivers/scsi/isci/ |
| D | phy.h | 74 * notification from the hardware that we restart the hardware OOB state
350 * type notification
352 * notification
354 * notification
360 * notification
362 * notification
364 * unsolicited frame notification
|
